wttr.in VS node

#!/bin/bash # Get weather information for a specified location LOCATION="London" curl "http://wttr.in/$LOCATION?format=3"

We’re going to use a free weather API, wttr.in, which gives us weather info just by calling a URL.

locals { url = format("https://wttr.in/%v?%v&format=%v&lang=%v&u=%v", urlencode(var.location), urlencode(var.options), urlencode(var.format), urlencode(var.lang), urlencode(var.units), ) } data "http" "weather" { url = local.url request_headers = { User-Agent = "curl" } } # Now write this to a file (as an example of a resource) resource "local_file" "cache" { filename = "cache.${var.stage}.txt" content = data.http.weather.response_body }

wttr.in is unfortunately not accurate in many cities in the world, check their github issues

The difference with weafetch is that it has its own config file which can just be configured and not touched anymore. When using wttr.in with curl, any custom changes you want to get from the output will need to be typed in everytime.

What about https://wttr.in/ ?

We’ll be using Node.js to run our code. If you don’t have Node.js installed, go to the Node.js website and download the latest version.

Make sure you have Bun or Node.js installed on your machine.

Download and install Node.js (npm is included with Node.js).

In the meantime, I started writing more and more isomorphic JavaScript (i.e., working both in client and server) and found Deno to be the perfect runtime for it. Deno relies on web standards rather than implementing its own like Node. Because of this, I encountered some compatibility issues, which shouldn't exist, as developers should be free to use whatever that suits them best, whether it's Node, Deno, Bun or the browser.

test_runner: add level-based diagnostic handling for reporter #55964

Now that the changes were made, it was time to test my work. To do this, I needed to build Node.js locally. I referred to the Building.md file for instructions. Before building, I had to install the prerequisites for my environment. The document mentioned three options for installing these prerequisites.

Node.js(v20.15.1)

Vitest does not support CommonJS mocking as of today.

I switched to Vitest because Jest was giving me flaky coverage results: https://github.com/nodejs/node/issues/51251

And while Vitest' coverage is stable, I had to add an indirection layer to change how I mock out calls to GitHub's API (@github/octokit).

Oh, side note: vite-node's --watch functionality does not restart the process. It does hot reloading which is different enough that it requires some rework at how you set up your app structure and callbacks.

Install Node.js: Head over to the Node.js website and download the latest version. Follow the installation instructions for your operating system.

Finally, I discovered a good issue in the Node.js repository. Node.js is a cross-platform JavaScript runtime environment that executes code outside of a browser, built on Chrome's V8 engine. I have worked extensively with Node.js, having built many projects using it, but I never imagined that one day I would get the opportunity to contribute to its core development. I reached out to the maintainer to ask if I could work on the issue.