Move a module from devDependencies to dependencies in npm package.json
Is there any short command to move a module from devDependencies to dependencies in package.json?
I find myself always doing this:
npm uninstall <module_name> --save-dev
npm install <module_name> --save
Is there a shorter approach to this?
package-lock.json, and merely marking the dependency as a dev dependency, then the approach mentioned in this answer should be the way to go: stackoverflow.com/a/57032462/3575560
Shorthand to move from devDependencies to dependencies (prod):
npm i <module_name> -P
If you want to do the opposite (i.e. move a module from dependencies to devDependencies) just do:
npm install <module_name> --save-dev
or shorthand:
npm i <module_name> -D
Yes! to move a module from devDependencies to dependencies:
npm install <module_name> --save-prod
In yarn:
Move a module from devDependencies to dependencies:
yarn remove <module_name> --dev && yarn add <module_name>
Move a module from dependencies to devDependencies :
yarn remove <module_name> && yarn add <module_name> --dev
As said in the comments, the command actually deletes the module and reinstall it in the new place.
dependencies to devDependencies without removing and re-adding?
&& with &.
The problem with using npm or yarn commands is that there is a chance that the version that is re-added is a different version than the one that is currently used. If this is what you want - both a move and an upgrade - then go ahead and use the accepted answer.
If not, simply manually edit your package.json to move the line from the devDependencies object to the dependencies object (creating it if necessary). You can go the other direction too.
The lock file doesn't hold any information about if things are prod or dev dependencies, so that doesn't need to be updated.
You can do a npm/yarn install afterwards to fix up any flags in the lock files.
dependencies top-level section in package-lock.json, each entry potentially has a dev flag to indicate whether it is a dev dependency or a transitive dependency of one. See docs.npmjs.com/files/package-lock.json#dev "If [dev is] true then this dependency is either a development dependency ONLY of the top level module or a transitive dependency of one. This is false for dependencies that are both a development dependency of the top level and a transitive dependency of a non-development dependency of the top level."
The issue of using npm install is that you end up with updated versions. What worked for me is:
Moving them to the intended part (dev, or prod) Removing them from node_modules folder Execute npm install
That kept all versions intact.
If your project doesn't have a lockfile or a shrinkwrap file yet, you can simply move the corresponding line in your package.json.
(I'm not recommending not using lockfiles)
I was trying to find an answer for this question for people that uses Yarn, but it hasn't a command for this matter yet. Although, I believe it is not essential anyway. Physically (in the Node modules folder) there are no difference between a dependency listed for production and the ones listed for development in your package.json, they'll go to the same place (node_modules). So, if you need to switch a dependency from devDependencies to dependecies you can go to your package.json and move manually with no need to run a new install or remove the dependency and then install it again with the dev flag. For me, it's not so great at all to manage the package.json manually, but Yarn is not as advanced as NPM in all functionalities, thus that's a thing to consider.
Follow WeChat
Success story sharing
Want to stay one step ahead of the latest teleworks?
Subscribe Now相似问题
- Is there a way to get version from package.json in nodejs code?
- How do you prevent install of "devDependencies" NPM modules for Node.js (package.json)?
- How do I completely uninstall Node.js, and reinstall from beginning (Mac OS X)
- "message failed to fetch from registry" while trying to install any module
- How can I uninstall npm modules in Node.js?
- How to specify local modules as npm package dependencies
- npm WARN package.json: No repository field
- What's the difference between dependencies, devDependencies and peerDependencies in npm package.json file?
- Why use peer dependencies in npm for plugins?
- How to install only "devDependencies" using npm
npm i module-example -Dwill also work to move from prod to dev, as well asnpm i module-example -Pto move from dev to prod dependenciesyarn remove <module_name>and then re-adding it into devDependencies withyarn add <module_name> --devdependenciestodevDependenciesinpackage.json? The lock file doesn't seem to store any information regarding dev or production