fix(guided remediation): npm workspaces devDeps in in-place strategy #1512
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
devDependencies
can be declared in a workspace, which is not a direct dependency (root
->workspace
->dev
). Made the IsDev check thatin-place
uses also check these so that--ignore-dev
works properly forin-place
with npm workspace.(
--ignore-dev
still doesn't behave correctly forrelax
with workspaces, but relax doesn't really work with workspaces anyway)Also fixed a potential panic with in-place & private registries that don't behave as expected w.r.t.
optionalDependencies
being in regulardependencies