Skip to content

Update npm audit 401 error message#112

Closed
simonua wants to merge 6 commits into
npm:release-nextfrom
simonua:feature/update-npm-audit-401-error-message
Closed

Update npm audit 401 error message#112
simonua wants to merge 6 commits into
npm:release-nextfrom
simonua:feature/update-npm-audit-401-error-message

Conversation

@simonua

@simonua simonua commented Dec 11, 2018

Copy link
Copy Markdown
Contributor

@simonua simonua requested a review from a team as a code owner December 11, 2018 15:59
@simonua simonua changed the title Feature/update npm audit 401 error message Update npm audit 401 error message Dec 11, 2018
@simonua simonua closed this Dec 11, 2018
@simonua simonua reopened this Dec 11, 2018
@simonua simonua changed the base branch from latest to release-next December 11, 2018 16:02
@simonua

simonua commented Dec 18, 2018

Copy link
Copy Markdown
Contributor Author

@zarenner, might be of interest to your group as well. Also posted on the Developer Community.

@simonua

simonua commented Dec 18, 2018

Copy link
Copy Markdown
Contributor Author

@zkat and I chatted about this, and I agree with her decision to not pursue this PR as it would obfuscate something that the third party registry should do better/differently here.

@simonua simonua closed this Dec 18, 2018
Jah-yee pushed a commit to Jah-yee/cli that referenced this pull request Apr 16, 2026
)

When glibc isn't compatible (Alpine, NixOS, Docker scratch images),
the npm install script falls back to a static musl binary. However,
no musl target was configured in dist-workspace.toml, causing the
fallback to fail with "Platform not supported".

Fixes npm#86
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants