-
Notifications
You must be signed in to change notification settings - Fork 12.3k
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
Typescript 5.5 is not working with yarn v4 and nodeLinker pnp, it forces switching to nodeLinker node-modules #58950
Comments
Sorry, it is hard to provide playground, because I see no sandboxes supports yarn in pnp mode. Please just use the following shell script:
Result is the following:
You can fix it by using the following shell script:
And it will finish without errors. |
This happens with roughly every new TypeScript release but it's not on the TypeScript team to handle this. You'll need to wait for yarnpkg/berry#6349 to be released or if you want you can use that PR version of Yarn by running the following in your project: yarn set version from sources --branch 6349
yarn install
You can "simplify" that to |
@merceyz, Thank you, it works perfect. Lets wait until it will be released. |
It was released 22 minutes ago https://github.com/yarnpkg/berry/releases/tag/%40yarnpkg%2Fcli%2F4.3.1 |
π Search Terms
Typescript 5.5 and yarn berry/canary/v3/v4/etc and pnp mode, found no bug reports.
π Version & Regression Information
β― Playground Link
No response
π» Code
Something has significantly changed from typescript
5.4.5
to5.5.0
.yarn config set nodeLinker pnp
was working fine together withyarn exec tsc
. Today I had to switch toyarn config set nodeLinker node-modules
in order to useyarn exec tsc
together with typescript5.5.0
.Typescript config is standard:
π Actual behavior
If you are trying to run
yarn exec tsc
(whenyarn
v4 is in pnp mode) than typescript 5.5.0 will fail with something like:π Expected behavior
yarn exec tsc
(whenyarn
v4 is in pnp mode) works without errors.Additional information about the issue
Did you break something related to
node_modules
dir in typescript 5.5.0? Thank you.The text was updated successfully, but these errors were encountered: