Previously, we have covered how to identify where the user is, based upon navigator.geolocation and based upon their IP address (there are definitely ways to make IP-based geolocation suck less). I figured that in today’s post, we would look at how to go from an arbitrary physical location (zip code or city name) to latitude and longitude coordinates. Continue reading Where art thou: Converting addresses to latitude and longitude.
Last week, I wrote about creating a cloudflare worker. When I created that worker, I knew that I wanted to leverage that for the state parks app. This week, I created three new workers: one to get the user’s location, one to get the list of parks, and one to get an individual park. Let’s take a look. Continue reading State Parks App: I made some new APIs for the app
The way I installed the lesson was:
npm install -g learnyounode
I had assumed that that would have placed code within my current directory, but it apparently installs it into some sort of global package directory. The “-g” is signifying “global”. Once the package is installed, it is executed by running “learnyounode” at the command line.
I have gotten through the first four items within the lesson. This weekend, I will finish the rest of them. I like this a lot. April’s 30-day challenge might involve writing a Node app.