Dependencies
suggest change“dependencies”: {
"module-name": "0.1.0"
}
- exact:
0.1.0
will install that specific version of the module. - newest minor version:
^0.1.0
will install the newest minor version, for example0.2.0
, but won’t install a module with a higher major version e.g.1.0.0
- newest patch:
0.1.x
or~0.1.0
will install the newest patch version available, for example0.1.4
, but won’t install a module with higher major or minor version, e.g.0.2.0
or1.0.0
. - wildcard:
\*
will install the latest version of the module. - git repository: the following will install a tarball from the master branch of a git repo. A
#sha
,#tag
or#branch
can also be provided: - GitHub:
user/project
oruser/project#v1.0.0
- url:
git://gitlab.com/user/project.git
orgit://gitlab.com/user/project.git#develop
- local path:
file:../lib/project
After adding them to your package.json, use the command npm install
in your project directory in terminal.
devDependencies
"devDependencies": {
"module-name": "0.1.0"
}
For dependencies required only for development, like testing styling proxies ext. Those dev-dependencies won’t be installed when running “npm install” in production mode.
Found a mistake? Have a question or improvement idea?
Let me know.
Table Of Contents