Skip to content
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 PNP support #408

Open
Suya1671 opened this issue Apr 30, 2022 · 2 comments
Open

Yarn PNP support #408

Suya1671 opened this issue Apr 30, 2022 · 2 comments

Comments

@Suya1671
Copy link

What version of this package are you using?
latest

What problem do you want to solve?
Adding support for yarn pnp

What do you think is the correct solution to this problem?
use yarn run ts-standard instead of whatever is going on currently when a .pnp.cjs file is detected

Are you willing to submit a pull request to implement this change?
Maybe ill try later

@showaltb
Copy link

I'm not qualified to create a PR for this, but could it be handled by implementing a setting to provide a custom command to run the linter? That way we could just use yarn run standard (or whatever) and the plugin wouldn't have to worry about PnP details.

Without this, the plugin runs the global version of standard, which is good, but has bitten me once or twice on some minor rule updates.

@timchambers
Copy link

I'm still having this issue with Yarn 4.0 which uses this PNP method that doesn't create a node_modules directory or expose binaries in the same fashion. Has anyone sorted out a workaround to get this working again when using Yarn?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

3 participants