You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The node_modules folder usually turns out to be quite a large folder, since it contains all the modules, but it also doesn't really serve any functionality on github since the installed packages are only needed when the code is to be deployed and run, which does not happen on github.
The package.json file is usually enough for this, and is the only info that we need, so that we can clone the repo and npm i to replicate things.
This reduces the size of the repo, and if you make any changes to the dependencies, then it also reduces the size of each push. Overall good practice, unless in some cases when you are deploying from github.
The text was updated successfully, but these errors were encountered:
The
node_modules
folder usually turns out to be quite a large folder, since it contains all the modules, but it also doesn't really serve any functionality on github since the installed packages are only needed when the code is to be deployed and run, which does not happen on github.The package.json file is usually enough for this, and is the only info that we need, so that we can clone the repo and
npm i
to replicate things.This reduces the size of the repo, and if you make any changes to the dependencies, then it also reduces the size of each push. Overall good practice, unless in some cases when you are deploying from github.
The text was updated successfully, but these errors were encountered: