After fork, the installation of dependencies with Yarn fails
See original GitHub issueDescribe the bug I’m not able to install dependencies with yarn in my forked repo.
To Reproduce
- Fork the repo
- In the terminal and in the repo’s folder, execute
yarn install
- The installation fails with an error related to:
https://github.com/pastelsky/webpack-4-modern.git#commit=fca4748eafe351bf9757c04ef9fcce2151c6ac14
I’m on windows 10 with node v16.13.1 as stated on the .nvmrc file.
Expected behavior The dependencies should be installed without issues.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
expected workspace package to exist · Issue #7807 · yarnpkg ...
Failed to install dependencies in workspace: expected workspace package ... The error started occurring after upgrading yarn to 1.19 and it ...
Read more >yarn install
If yarn.lock is absent, or is not enough to satisfy all the dependencies listed in package.json (for example, if you manually add a ......
Read more >How to fork a dependency and use it locally in a project
It's necessary to run yarn in the directory of the 3rd party library first to install the dependencies there then the application should...
Read more >How to Use Forked NPM Dependencies in React | Pluralsight
In order to install a forked dependency into your project or app, you first need to create a fork! Creating a forked repository...
Read more >How to install package from github repo in Yarn - Stack Overflow
You can add any Git repository (or tarball) as a dependency to yarn by specifying the remote URL (either HTTPS or SSH):
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
So you were right. A newly cloned folder didn’t repro it either. I’d to clear all of my yarn cache. Anyhow, I’ve now updated the checksum to the correct one, and added a CI check as well which is green. Thanks for reporting this, but I believe we can now close this issue.
Duplicate https://github.com/pastelsky/bundlephobia/issues/707. Could you try the suggestion here ?