Node Version Manager and failing certificate verification

Published:

Node.js

In my current job, we have some kind of network settings ( or better proxy settings ) that from time to time cause problems with certificate verification.

nvm ls-remote

I used nvm to install node and npm on my computer. Few days ago I needed to change my node version to newer one. It is very easy with nvm, you just list all versions and choose which one you want. So I typed…

$ nvm ls-remote

This command should list all available versions of node. But all I got was :

N/A

The problem in this case is with certificate verification. Nvm doesn’t have any option to disable this, but when you read the docs carefully, there is option to set $NVM_NODEJS_ORG_MIRROR variable. So you can do the following :

$ export NVM_NODEJS_ORG_MIRROR=http://nodejs.org/dist

And now everything works, because there is no need to check certificate when it is only http. The nvm ls-remote command outputs :

v0.1.14
v0.1.15
v0.1.16
...
v8.8.1
v8.9.0   (Latest LTS: Carbon)
v9.0.0

And then you can install any version you want :

$ nvm install <version>

References

GitHub – nvm

Introduction to Sequelize ORM titleee

This is about the basic usage of Sequelize ORM – how to create migrations, models, seeders and how to get the data from the database. Everything is explained on an example project, which you can find on GitHub.

Read more
Express server with JWT authentication titleee

I needed to create a simple server, that would have one “public” route /login and other routes are available only for users with valid JWT token.

That means, the user is allowed to log into the system and then get any data from it. If he is not logged in and he tries to get some data, he only get an error message and 401 ( Unauthorized ) status code will be returned.

Read more