I’ve heavily promoted nvm, a Node.js version manager, over the years. Having a tool to manage multiple versions of a language interpreter has been so useful, especially due to the complexity of Node.js package management.
One tip I like to give new developers is adding a
.nvmrc file to their repositories. The file contents is just a simple string representing the version of Node.js the project requires:
A project with this
.nvmrc is specifying that Node.js
v16 should be used. Any developer could then run
nvm use to download, install, and switch to that version. A
nvm install call would then install dependencies in line with that version.
One of the worst kept secrets about AJAX on the web is that the underlying API for it,
XMLHttpRequest, wasn’t really made for what we’ve been using it for. We’ve done well to create elegant APIs around XHR but we know we can do better. Our effort to…
If you’re like me and lay awake in bed at night, you’ve flipped on the TV and seen the commercials: misguided, attention-starved college girls fueled by alcohol ruining their futures by flashing lame camera-men on Spring Break. Why do they do it? Attention…