-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
--link-duplicates error #2734
Comments
I am meeting this too, essentially I cannot use the option because it doesn't work reliably. |
Can't fetch a private package IIRC An unexpected error occurred: "https://registry.yarnpkg.com/@kadira/storybook-addon-links/-/storybook-addon-links-1.0.1.tgz: Request failed "503 Service Unavailable"". |
I wonder if the error is related to @ in file path |
@bestander would it help if I figured out another reproduction case? |
Of course |
Even more help would be to find out the cause of the issue, the core linking logic is implemented here https://github.com/yarnpkg/yarn/blob/master/src/util/fs.js#L513 and here Line 232 in 0ad2bf9
|
Is this issue still being tracked? |
Afaik no one in the core team is actively working on fixing that, help from the community is expected. |
With the new [email protected] an error appears when I use Steps to reproduce: mkdir test && cd test
yarn add webpack webpack-stream webpack-dev-middleware --link-duplicates result:
I tested it using several version combinations: |
looking into it now |
* fixed #2734 * added another test * fixes for Mael * prettier * added comment
Do you want to request a feature or report a bug?
This is a bug in the pre-release
0.21.2
version with the--link-duplicates
flag.What is the current behavior?
Installing a project with
@kadira/storybook
andwebpack@2
results in the following error:Please mention your node.js, yarn and operating system version.
Node 6.9.2, Yarn 0.21.2, OSX Sierra.
Reproduction Repository
A reproduction is available.
Ref: #2620 (comment) and this tweet. My preference would be for the feature to remain as it gives us significant (20%) size savings on our frontend project.
The text was updated successfully, but these errors were encountered: