replace deprecated registry.npmjs.cf with registry.npmjs.org
#63
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
SukkaW
force-pushed
the
replace-npm-registry
branch
from
8ff7c5c
to
cf03655
Compare
styfle
approved these changes
Aug 14, 2023
|
@anvaka Kindly request your attention with a friendly ping. It has been more than 2 weeks since I opened this PR. I would greatly appreciate it if you could spare some time to review it, at your convenience, and provide your valuable feedback. |
|
Thank you, this is deployed now. |
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.
The PR closes #62.
npmjs.cfis being deprecated: npmjs-cf/meta#8Since now
registry.npmjs.orgnow also has CORS support (npm/feedback#117 (comment)), the PR replacesregistry.npmjs.cfwithregistry.npmjs.org.