ERR_TLS_CERT_ALTNAME_INVALID when doing npm i

[Abernachy]

Hey, just like a heads up, when going through the Serverless stuff, forking and attempting to install the node modules for course4 exercises gives you an error.

The reason is because its attempting to snag the AWS, axios, and other packages from the nexus solutions url in the package-lock file., which doesn't work. To fix this on my end, I deleted the package-json and then removed the aws-sdk dependency from the package.json file. Then I just ran 'npm i aws-sdk' which installed the 2.11100 version. Then I ran 'npm i' to install the other packages and their dependencies and to have it auto generate a new package-lock.json file and voila, everything works now.

If you just try to edit the package.json file and add the 2.1110 as the aws-sdk version it will still error out because the other packages in package-lock are pointing to the nexus solutions endpoints rather than npm endpoints.

[ifyoma]

woow thanks alot for this

[SudKul]

Thanks, @Abernachy
It's a smart choice to delete the package-lock.json and recreate a new one specifically for your platform.
I think you have fixed this in #384, right?