You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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?
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 detectedAre you willing to submit a pull request to implement this change?
Maybe ill try later
The text was updated successfully, but these errors were encountered: