-
Notifications
You must be signed in to change notification settings - Fork 40
Issues: npm/npm-registry-fetch
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[BUG] thing that needs fixing
Needs Triage
needs an initial review
opts.noproxy
definition in README is outdated
Bug
#172
by lingyuncai
was closed Apr 13, 2023
1 task done
[FEATURE] Support sending custom request headers to a registry (
$MY_AUTH_HEADER: $VALUE
)
#145
by TysonAndre
was closed Oct 13, 2022
[DOCS] Out of date documentation w.r.t. support for top-level auth options
#63
by treykasada
was closed Feb 9, 2022
[BUG] Get started exemple not works "uri.trim is not a function"
#56
by c0ncentus
was closed Feb 9, 2022
[QUESTION] is the legacy global _auth setting not supported?
#47
by ryhinchey
was closed May 2, 2021
[BUG] cache and registry in combination makes fetch unstable
#23
by pgsandstrom
was closed May 13, 2020
[QUESTION] How can I use authentication for npm registry but skip authentication when accessing github?
#12
by miguelsosa
was closed Apr 22, 2021
Ensure
registry
option is enforced even when package-lock.json
has different resolved
#7
by darcyclarke
was closed Sep 17, 2019
3 tasks done
ProTip!
Add no:assignee to see everything that’s not assigned.