Problem with Putout when using Yarn v3 PNP
See original GitHub issueSteps to reproduce:
npx create-next-app@latest --ts
cd next-ts
yarn add --dev eslint-config-hardcore
# Add hardcore configs to .eslintrc.json
rm -rf node_modules package-lock.json yarn.lock
yarn set version berry
yarn
yarn lint
Expected behavior: should run ESLint successfully
Actual behavior: Error: Error while loading rule 'putout/putout': Plugin "putout-plugin-apply-shorthand-properties" could not be found!
Moved from https://github.com/EvgenyOrekhov/eslint-config-hardcore/issues/385
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Extraneous dependencies with Yarn v3 #93 - GitHub
When I try to use Putout with Yarn v3, I get the following error: @putout/formatter-progress-bar: simport tried to access ...
Read more >Plug'n'Play | Yarn - Package Manager
An overview of Plug'n'Play, a powerful and innovative installation strategy for Node.
Read more >Need help setting up eslint in a monorepo using Yarn 3 and ...
So my question is : Is there any way to only declare the ESlint plugin depenencies ONCE (in the config project) and not...
Read more >[AskJS] Is someone using Yarn v2 in business? - Reddit
We decided that Yarn 2.1 would implement what we call a PnP-loose mode, inspired in idea by the loose mode in Babel. In...
Read more >Yarn 3.0 Performances, ESBuild, Better Patches
That alone should address most of the problems you may have been hitting ... When using Yarn 3 w/ PnP, the exports field...
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 Free
Top 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
Thanks for the hardwork. 👍
@coderaiser I agree, it’s not worth it. We should wait until Yarn v3 becomes stable.
@spa5k We’ve done what we could. Apparently Yarn v3 is just raw and buggy.
Workaround: use npm.