Should you commit node_modules to Git?

For reference, npm FAQ answers your question clearly: Check node_modules into git for things you deploy, such as websites and apps. Do not check node_modules into git for libraries and modules intended to be reused. Use npm to manage dependencies in your dev environment, but not in your deployment scripts.

Do I need to include node_modules in production?

The consensus answer, in general is YES – I still need the node_modules directory during runtime. I am also not asking about running npm init or npm install. Or, will I still need that directory during runtime? This is for a basic front end, client side web application only.

Why you shouldn’t commit node_modules?

Not committing node_modules implies you need to list all your modules in the package. json (and package-lock. json ) as a mandatory step. This is great because you might not have the diligence to do so, and some of the npm operations might break if you don’t.

Do you need to upload node_modules?

You should, typically, not upload node modules folder manually. They are the external libraries and are easily available to install separately. So, when moving files through filezilla, move everything but node modules. No need to copy the node_modules folder at all.

What happens if I delete node_modules?

You could remove your node_modules/ folder and then reinstall the dependencies from package. json.,This would erase all installed packages in the current folder and only install the dependencies from package.

Should I upload node_modules to server?

What is the purpose of node modules in angular?

The node_modules directory is only for build tools. The package. json file in the app root defines what libraries will be installed into node_modules when you run npm install . Very often with an angular app, on your dev machine or on a build server, you use other Javascript libraries from npm (a node.