-
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
yarn workspace don't resolve exactly version package #8606
Comments
@nvthuong1996 have you tried adding // landingpage/package.json
{
"name": "landingpage",
// ...
"resolutions": {
"react": "17.0.0" // <- specific required version
}
}
// webapp/package.json
{
"name": "webapp",
// ...
"resolutions": {
"react": "16.0.0" // <- specific required version
}
} |
i allready try but it not working.
|
I am facing a similar problem. I removed the I had a yarn.lock inside each individual workspace, but no yarn.lock in the project root. It appears that yarn ignores the inside yarn.locks. In my usecase, I am creating a mono repo of existing repositories. I think yarn should also check the inside workspace yarn.lock files to install the correct version of the package and build the root yarn.lock according to that. |
any progress? faced the same problem as described above |
I has two package in mono project use yarn workspace
package1: landingpage
package2: webapp
Dependency:
I use nohoist
When i run
yarn
to install packagelandingpage install react@17 but i found react@16 in ant package:
Landingpage use react@16 and react@17 => error
Please help me !!
The text was updated successfully, but these errors were encountered: