Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] npm config throws/becomes unusable after setting workspaces or workspace config #2941

Closed
darcyclarke opened this issue Mar 24, 2021 · 1 comment · Fixed by #2945
Closed

[BUG] npm config throws/becomes unusable after setting workspaces or workspace config #2941

darcyclarke opened this issue Mar 24, 2021 · 1 comment · Fixed by #2945
Assignees
@nlf
Labels
Bug thing that needs fixing Priority 0 will get attention right away Release 7.x work is associated with a specific npm 7 release

Comments

@darcyclarke
Copy link
Contributor

darcyclarke commented Mar 24, 2021 •
edited
Loading

Current Behavior:

  • npm config throws errors & becomes unusable when it sees defined workspaces or workspace config

Expected Behavior:

  • npm config should be exempt from this default behavior & not throw errors when it sees defined workspaces or workspace options (its core function/utility is to get/set that config)

Steps To Reproduce:

  1. npm config set workspaces=true
  2. npm config ... throws

Environment:

  • OS: osx
  • Node: 10.24.0
  • npm: 7.7.1
@darcyclarke darcyclarke added Release 7.x work is associated with a specific npm 7 release Bug thing that needs fixing Needs Triage needs review for next steps labels Mar 24, 2021
@darcyclarke darcyclarke added Priority 0 will get attention right away and removed Needs Triage needs review for next steps labels Mar 24, 2021
@darcyclarke darcyclarke changed the title [BUG] npm config continues to throw/becomes unusable after setting workspaces or workspace config [BUG] npm config throws/becomes unusable after setting workspaces or workspace config Mar 24, 2021
@nlf nlf mentioned this issue Mar 24, 2021
Merged
@nlf nlf self-assigned this Mar 24, 2021
@wraithgar
Copy link
Member

This should be fixed in v7.7.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nlf nlf

Labels
Bug thing that needs fixing Priority 0 will get attention right away Release 7.x work is associated with a specific npm 7 release
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: config should not error when workspaces are configured npm/cli
4 participants
@wraithgar @ruyadorno @nlf @darcyclarke