@patrickhund no, npm install express@3.0.0 will get you exactly version 3.0.0. Npm install in terminal (on the same directory where the package.json exists) and it would. I am having issues getting npm to install properly.
Two Paths Converged A Journey of Love, Growth, & Unity Las Vegas PRIDE
In the new version of npm (v7), by default, npm install will fail when it encounters conflicting peerdependencies. If you want to install all the node_modules from the package.json file you simply put: Take a look here for more info about peer.
Nvm is only for changing node.
The problem i faced (in windows computer) when i was trying to install a couple of npm packages i got the following error: See the docs for more detail. It was not like that before. I have tried stepping through the instructions on several of the posts here on stack overflow, specifically from this thread:
35 to install npm on windows just unzip the npm archive where node is. Npm is shipped with node, that is how you should install it. There is no difference, since npm i is an alias for npm install. Npm install express@^3.0.0 would get you the latest 3.x.x.
The install worked, but i'm not sure whether it was a good idea to solve it this way, because i don't quite understand the flag, that's why.
