Closed iDVB closed 2 years ago
Turns out our issue what that we we're not using the proper nodeLinker.
We had it as node_modules
and it was supposed to be node-modules
.
Btw, who's decision was it to use a hyphen here?! 😅
I'll reopen this as the error you included in the description is a real issue not related to the value in nodeLinker
In case anyone's coming from search — I had a similar error and was able to fix it by just deleting my private package's entry in my yarn.lock
file before running yarn install
Fix has been released as 3.2.0-rc.9
(https://github.com/yarnpkg/berry/commit/16d65d77ad35dfbe184f305b9bbfaf70a61e0adb)
yarn set version berry && yarn set version canary
Turns out our issue what that we we're not using the proper nodeLinker. We had it as
node_modules
and it was supposed to benode-modules
.Btw, who's decision was it to use a hyphen here?! 😅
Just got bit by this as well. It should crash for unsupported values and tell you why IMO
Self-service
Describe the bug
After migrating from Yarn v1 -> v3 and running
yarn install
I get...this happens for both
@ourscope/react-components
and@ourscope/eslint-config-react
One thing that seems odd is the Request URL having a
/-/
in it. and visiting that url in a browser nets with this...~/.yarnrc.yml (user home dir)
.yarnrc.yml (repo root)
Removing the
npmAuthToken
indeed errors with a not authorized error... so it seems the token is working properly.package.json (workspace's package.json)
To reproduce
It's a private repo and token so not sure how to provide repro steps?
Environment
Additional context
The above was all done in a repo that already worked in
v1
withworkspaces
. We just tried an empty folder...yarn init
yarn set version berry
yarn init
(needed to run twice for some reason)yarn add @ourscope/react-components
and everything worked as expected... no issues and this would be with the same
~/.yarnrc.yml
as above.