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
{{ message }}
This repository has been archived by the owner on Jan 8, 2021. It is now read-only.
npm-workspace install skips installing a devDependency if the target file already exists, even if the installed module version does not meet the defined version requirements.
npm-workspace install will result in [email protected] being installed in node_modules, while npm install will result in [email protected] being installed.
My particular use case will be resolved when we update the higher level modules depending on an old and busted version of fs-extra, but I wanted to identify the inconsistent behavior. Workaround is to do npm-workspace install && npm i.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
npm-workspace install
skips installing a devDependency if the target file already exists, even if the installed module version does not meet the defined version requirements.Take the following example
package.json
:npm-workspace install
will result in[email protected]
being installed innode_modules
, whilenpm install
will result in[email protected]
being installed.My particular use case will be resolved when we update the higher level modules depending on an old and busted version of
fs-extra
, but I wanted to identify the inconsistent behavior. Workaround is to donpm-workspace install && npm i
.The text was updated successfully, but these errors were encountered: