You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Possible bug, depending on whether yarn is meant to handle this or not.
What is the current behavior?
yarn upgrade has replaced resolved URLs for packages previously at https://registry.yarnpkg.com with http://registry.npmjs.org, e.g:
babel-plugin-syntax-async-functions@^6.8.0:
version "6.13.0"
- resolved "https://registry.yarnpkg.com/babel-plugin-syntax-async-functions/-/babel-plugin-syntax-async-functions-6.13.0.tgz#cad9cad1191b5ad634bf30ae0872391e0647be95"
+ resolved "http://registry.npmjs.org/babel-plugin-syntax-async-functions/-/babel-plugin-syntax-async-functions-6.13.0.tgz#cad9cad1191b5ad634bf30ae0872391e0647be95"
What is the expected behavior?
If the choice of scheme http vs https is handled by yarn, ideally this would be resolving to https to help avoid MITM attacks, so the above diff would be:
babel-plugin-syntax-async-functions@^6.8.0:
version "6.13.0"
- resolved "https://registry.yarnpkg.com/babel-plugin-syntax-async-functions/-/babel-plugin-syntax-async-functions-6.13.0.tgz#cad9cad1191b5ad634bf30ae0872391e0647be95"
+ resolved "https://registry.npmjs.org/babel-plugin-syntax-async-functions/-/babel-plugin-syntax-async-functions-6.13.0.tgz#cad9cad1191b5ad634bf30ae0872391e0647be95"
Please mention your node.js, yarn and operating system version.
Node: v10.9.0
Yarn: 1.9.4
OS: Mac OS X 10.13.6 (17G65)
The text was updated successfully, but these errors were encountered:
What’s the best way to upgrade the yarn.lock file after upgrading from 1.9.4 to >1.10.0 to fix the http://registry.npmjs.org issue? I’ve tried yarn upgrade but that includes unwanted upgrades and manual find/replace seems hacky. Is there something like yarn upgrade that preserves all existing versions (preventing a large testing effort on the app) while replacing the wrong registry and also adding integrity field in yarn.lock file?
Do you want to request a feature or report a bug?
Possible bug, depending on whether
yarn
is meant to handle this or not.What is the current behavior?
yarn upgrade
has replaced resolved URLs for packages previously athttps://registry.yarnpkg.com
withhttp://registry.npmjs.org
, e.g:What is the expected behavior?
If the choice of scheme
http
vshttps
is handled byyarn
, ideally this would be resolving tohttps
to help avoid MITM attacks, so the above diff would be:Please mention your node.js, yarn and operating system version.
Node: v10.9.0
Yarn: 1.9.4
OS: Mac OS X 10.13.6 (17G65)
The text was updated successfully, but these errors were encountered: