-
Notifications
You must be signed in to change notification settings - Fork 332
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 pacote with npm-registry-fetch #1329
Merged
Merged
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
raineorshine
force-pushed
the
npm-registry-fetch
branch
2 times, most recently
from
September 13, 2023 00:56
0b5855d
to
0113a20
Compare
raineorshine
force-pushed
the
main
branch
4 times, most recently
from
September 13, 2023 16:15
03526e5
to
66f2c08
Compare
raineorshine
force-pushed
the
npm-registry-fetch
branch
from
September 16, 2023 22:30
0113a20
to
f4a08f5
Compare
raineorshine
force-pushed
the
main
branch
3 times, most recently
from
October 4, 2023 21:50
c05c239
to
e416363
Compare
raineorshine
force-pushed
the
npm-registry-fetch
branch
2 times, most recently
from
November 3, 2023 15:55
dd1eabf
to
863c4c3
Compare
This comment was marked as outdated.
This comment was marked as outdated.
raineorshine
force-pushed
the
v17-next
branch
from
November 5, 2023 03:58
feca4e6
to
8c7c8f6
Compare
raineorshine
force-pushed
the
npm-registry-fetch
branch
from
November 5, 2023 04:13
863c4c3
to
c3992ae
Compare
raineorshine
force-pushed
the
v17-next
branch
4 times, most recently
from
November 5, 2023 21:44
7789c72
to
aa6cb24
Compare
raineorshine
force-pushed
the
npm-registry-fetch
branch
from
November 6, 2023 17:09
c3992ae
to
a2b3d4c
Compare
3 tasks
raineorshine
force-pushed
the
npm-registry-fetch
branch
from
November 21, 2023 23:38
a2b3d4c
to
544a565
Compare
raineorshine
force-pushed
the
npm-registry-fetch
branch
from
November 23, 2023 14:31
544a565
to
4b411b8
Compare
raineorshine
force-pushed
the
npm-registry-fetch
branch
from
November 24, 2023 00:20
4b411b8
to
c5a6dc4
Compare
raineorshine
force-pushed
the
npm-registry-fetch
branch
from
November 24, 2023 23:47
c5a6dc4
to
b0b9c7d
Compare
This comment was marked as resolved.
This comment was marked as resolved.
raineorshine
force-pushed
the
npm-registry-fetch
branch
from
March 27, 2024 21:16
9b64c37
to
377a47f
Compare
1 task
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.
Replace
pacote
withnpm-registry-fetch
to reduce the bundle size.There is some risk that the request headers are not recreated accurately, so this should wait for a major version change to be safe.