> Accept: */ * > Accept-Encoding: deflate, gzip * issuer: C=GB,ST=Greater Manchester,L=Salford,O=Sectigo Limited,CN=Sectigo RSA Domain Validation Secure Server CA * certificate version: #3 * subject: OU=Domain Control Validated,OU=PositiveSSL Wildcard,CN= *. * server certificate status verification SKIPPED

* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256 * found 516 certificates in /etc/ssl/certs I found that this is quite easy to do, but requires some configuration in your package.* Connected to (104.20.23.46) port 443 ( #0) * found 129 certificates in /etc/ssl/certs/ca-certificates.crt So I needed a way to instruct those that are trying to build my repository for this site, to tell it specifically what version of npm/node to use. After a lot of digging, I started to realize that this solution only optimally runs on a very specific version of Node and NPM. Obviously the build system that runs when Netlify detects a change to the source code or a triggered build is fired when I’ve created a new article, would be another system that needs to build the repository. But recently I was experiencing weird issues with different environments and the source not always building consistently across multiple machines. Some of you may know that this site is hosted on Netlify.

Change nvm version