-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
replace npm-registry-client with npm-registry-fetch #2
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zkat
force-pushed
the
zkat/registry-fetch-replacement
branch
from
July 27, 2018 01:22
5f5be69
to
bb23517
Compare
zkat
force-pushed
the
zkat/registry-fetch-replacement
branch
2 times, most recently
from
August 16, 2018 03:02
0c0b7c9
to
ae8d856
Compare
zkat
force-pushed
the
zkat/registry-fetch-replacement
branch
2 times, most recently
from
August 16, 2018 22:36
c4dcf07
to
765ff09
Compare
zkat
added
semver:minor
new backwards-compatible feature
and removed
semver:patch
semver patch level for changes
labels
Aug 16, 2018
switching to |
zkat
force-pushed
the
release-next
branch
2 times, most recently
from
August 20, 2018 23:19
05ab727
to
1bc5b8c
Compare
zkat
force-pushed
the
zkat/registry-fetch-replacement
branch
from
August 21, 2018 02:48
e05cd01
to
c4dfe41
Compare
zkat
force-pushed
the
zkat/registry-fetch-replacement
branch
6 times, most recently
from
August 28, 2018 23:15
78349e8
to
bc32f8b
Compare
zkat
force-pushed
the
zkat/registry-fetch-replacement
branch
2 times, most recently
from
November 26, 2018 23:28
4b3ce12
to
aef679f
Compare
3 tasks
zkat
force-pushed
the
zkat/registry-fetch-replacement
branch
from
November 27, 2018 19:20
9307703
to
faa224c
Compare
zkat
force-pushed
the
zkat/registry-fetch-replacement
branch
from
November 27, 2018 19:54
faa224c
to
fcdbeae
Compare
4 tasks
isaacs
added a commit
that referenced
this pull request
Aug 12, 2019
- [`9c93ac3`](npm/cmd-shim@9c93ac3) [#2](npm/cmd-shim#2) [#3380](npm/npm#3380) Handle environment variables properly ([@basbossink](https://github.com/basbossink)) - [`2d277f8`](npm/cmd-shim@2d277f8) [#25](npm/cmd-shim#25) [#36](npm/cmd-shim#36) [#35](npm/cmd-shim#35) Fix 'no shebang' case by always providing `$basedir` in shell script ([@igorklopov](https://github.com/igorklopov)) - [`adaf20b`](npm/cmd-shim@adaf20b) [#26](npm/cmd-shim#26) Fix `$*` causing an error when arguments contain parentheses ([@satazor](https://github.com/satazor)) - [`49f0c13`](npm/cmd-shim@49f0c13) [#30](npm/cmd-shim#30) Fix paths for MSYS/MINGW bash ([@dscho](https://github.com/dscho)) - [`51a8af3`](npm/cmd-shim@51a8af3) [#34](npm/cmd-shim#34) Add proper support for PowerShell ([@ExE-Boss](https://github.com/ExE-Boss))
What about this Issue? I am still having this behaviour, that the noproxy setting for a domain does not work. https://npm.community/t/npm-publish-doesnt-respect-noproxy-configuration/2464/4 |
Closed
1 task
1 task
2 tasks
1 task
Closed
2 tasks
2 tasks
antongolub
pushed a commit
to antongolub-forks/npm-cli
that referenced
this pull request
May 18, 2024
* Finish fully promisifying * Cleanup isHashbangFile implementation * Only do dos2unix pass when CRs are present in hashbang file * Rewrite dos2unix to not use streams * Only convert shebang CR when converting CRs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is the beginning of the work needed to finally obsolete
npm-registry-client
in favor ofnpm-registry-fetch
. I'm starting with more trivial commands, making sure they work, and then working my way up to more involved commands.TODO - commands that use
npm-registry-client
directlynpm view
npm star
npm stars
npm deprecate
npm ping
npm whoami
figgy-pudding
config for npm stufflib/utils/metrics.js
npm dist-tag
npm outdated
npm owner
npm team
npm access
npm org
(PR didn't get merged. Should port anyway)npm search
npm logout
npm login/adduser
(should be mainly just the legacy npmE bits)npm publish
npm unpublish
npm ci
TODO - need to be ported to
figgy-pudding
/new pacotenpm install
npm pack
npm ci
(uggghhh)npm audit
npm audit fix