Skip to content
This repository has been archived by the owner on Jan 8, 2021. It is now read-only.

devDependencies skipped when incorrect version exists #36

Open
schmidtk opened this issue Oct 27, 2016 · 0 comments
Open

devDependencies skipped when incorrect version exists #36

schmidtk opened this issue Oct 27, 2016 · 0 comments

Comments

@schmidtk
Copy link

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:

{
  "name": "test",
  "version": "0.1.0",
  "devDependencies": {
    "ncp": "^2.0.0"
  },
  "dependencies": {
    "fs-extra": "^0.12.0"
  }
}

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant