-
Notifications
You must be signed in to change notification settings - Fork 4k
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
fix: use registry.npmjs.com to fix shinkwrap resolves #16607
Conversation
924c117
to
ebfd5f2
Compare
Pull request has been modified.
The CodeBuild step fails but I have to log in to view the details. Can you check what's wrong or explain how to test locally?
|
The commands from buildspec fail the same way on my branch and upstream.
Test failed even after installing boto3 |
Pull request has been modified.
Use the npm registry instead of yarns mirror. npm treats registry.npmjs.org as a special value that means 'the current configured package' in package-lock and npm-shrinkwrap. if we use registry.yarnpkg.com in our shrinkwrap then users with a custom registry will be forced to registry.yarnpkg.com. npm/cli#3783 I updated yarn.lock with sed. ``` sed 's|https://registry.yarnpkg.com|https://registry.npmjs.org|' yarn.lock -i ```
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
npm treats registry.npmjs.org as a special value that means 'the current configured package' in package-lock and npm-shrinkwrap. npm will request aws-cdk's dependencies from yarnpkg instead of from the installers configured registry because aws-cdk's shrinkwrap uses yarnpkg. This behavior seems new to [npm v7]. It causes issues for us because we run our builds with a isolated network and a private registry. [npm v7]: npm/cli#3783 This commit changes the registry from yarnpkg to npmjs. I updated yarn.lock with sed. ``` sed 's|https://registry.yarnpkg.com|https://registry.npmjs.org|' yarn.lock -i ``` Alternatively we could modify the yarn-cling tool to replace the registry. [registry.yarnpkg.com is a cname for registry.npmjs.org](https://yarnpkg.com/getting-started/qa#why-registryyarnpkgcom-does-facebook-track-us) so changing to registry.npmjs.org shouldn't affect available packages or performance. ``` dig registry.yarnpkg.com | rg CNAME registry.yarnpkg.com. 300 IN CNAME yarn.npmjs.org ``` ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
npm treats registry.npmjs.org as a special value that means 'the current configured package' in package-lock and npm-shrinkwrap. npm will request aws-cdk's dependencies from yarnpkg instead of from the installers configured registry because aws-cdk's shrinkwrap uses yarnpkg. This behavior seems new to npm v7. It causes issues for us because we run our builds with a isolated network and a private registry.
This commit changes the registry from yarnpkg to npmjs. I updated yarn.lock with sed.
Alternatively we could modify the yarn-cling tool to replace the registry. registry.yarnpkg.com is a cname for registry.npmjs.org so changing to registry.npmjs.org shouldn't affect available packages or performance.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license