 Hi, folks. I'm Jordan, and I maintain NVM, which is a widely used Node version manager. There's lots of reasons a version manager for Node is useful. If you're offering packages, it's important to be able to locally test in different Node versions. And if you're running an app and preparing to upgrade from, say, Node 10 to Node 12, it's really helpful to be able to quickly switch between them so you can ensure that the upgrade will be as low risk as possible. For most users, installing NVM is a one line command found in the projects readme. If you have any trouble, please file an issue and fill out the full template, and I'll do my best to help. After installing NVM, the first thing you'll want to do is install a Node version. So we have to decide which one. I'd recommend starting with the latest version. So for that, you'd type nvm install node. This will download and install a binary or compile from the source if needed, and then we'll use it, which you can verify with nvm current. NVM will also cache the downloaded archive so you don't have to download it more than once. The first time that you install a Node version, NVM will set it as the default alias, which means that it will be auto-used when the shell starts. You can check this with nvm alias, or nvm ls, which includes the alias listing. You'll see the default pointing to version 14.4.0, and n slash a are not applicable for most of the others. All the yellow ones represent LTS release lines, which stands for long-term support. You can use LTS slash star, LTS slash erbium, et cetera, as a shortcut to install that LTS version. So now let's install some more Node versions. I'm going to type nvm install LTS slash argon, which installs version 4.9.1, the last supported version in the argon release line, which is now end of life. And with nvm ls, we can verify this. And as you can see, version 4.9.1 is installed. The arrow means that's the current version. And the LTS argon alias points to it down at the bottom. So you can get the latest LTS version with nvm install dash dash LTS, which at this time is version 12.18.0. And with nvm ls, we can see that that's installed. The arrow means it's current because it's been used. It's LTS slash erbium. And LTS slash star also points to the latest one, which at the moment, the latest installed one, which at the moment is that. Now that we have three versions installed, we can switch between them with nvm use. So in this case, I typed 14. You can type 14.4 or 14.4.0. You can also use LTS slash argon or any of the other aliases. The custom aliases are supported as well. And nvm use dash dash LTS is a shortcut for LTS slash star, which is the same thing. And these all use your locally installed versions, not the remote ones, only when installing. So this is a check what's available. And for any commands, you can check nvm dash dash help to see what's available with hopefully a helpful explanation. And if you have any questions, please feel free to file an issue and ask. Last October, nvm became the first project to join the newly merged OpenJS Foundation. The primary goals for being part of the foundation are to ensure that the project survives long term and can grow beyond its current state, which is having a single maintainer. Here is a few things that I'm focusing on for nvm over the next year. The main one is speed improvements. nvm invokes npm when you're using a version. And this is quite slow for some users. This needs to be fixed, but without bringing back the bugs that invoking npm prevents. The next thing is official support for release candidates and nightly builds of Node. This is already possible with a few hacks, but I want it to be properly supported. The next one is the ability for nvm to automatically update itself. So you don't have to keep looking up the install script to grab the new version number. And then the last big one is testing. The current tests that nvm uses to validate itself are cumbersome to write and, more importantly, to read. And we need a better solution. So you might be asking yourself, how can I help? The big one, of course, is contributing. You can find an issue with the pull request wanted label and gonettes. But remember, the most important kind of contributions are not code. They're making documentation more intuitive and approachable. They're reproducing reported issues and distilling reports into failing test cases, things like that. And if you don't have the time to contribute, that's fine. There's also sponsorship available via GitHub. That helps as well. Thanks, everybody. And look forward to hearing about all the great ways you're all using nvm.