Skip to content

Commit

Permalink
docs: README: OnP -> PnP
Browse files Browse the repository at this point in the history
  • Loading branch information
coderaiser authored Nov 1, 2024
1 parent e8d2cce commit 320818a
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ are also supported. Here is how it looks like:
- [🛴 Codemods](#-codemods)
- [⏣ Integration with ESLint](#-integration-with-eslint)
- [☄️ Integration with Babel](#%EF%B8%8F-integration-with-babel)
- [🐈 Integration with Yarn OnP](#-integration-with-yarn-pnp)
- [🐈 Integration with Yarn PnP](#-integration-with-yarn-pnp)
- [⛓ Using Putout as Loader](#-using-putout-as-loader)
- [🚪 Exit Codes](#exit-codes)
- [🦔 Real-world uses](#-real-world-uses)
Expand Down Expand Up @@ -2836,15 +2836,15 @@ Just create `.babelrc.json` file with configuration you need.
}
```

## 🐈 Integration with Yarn OnP
## 🐈 Integration with Yarn PnP

Since 🐊**Putout** has dynamic nature of loading:

- `plugins`;
- `processors`;
- `formatters`;

It was a nice adventure to have support of such a wonderful feature of `Yarn` as [`Plug'n'Play`](https://yarnpkg.com/features/pnp).
It was a nice adventure to add support of such a wonderful feature of `Yarn` as [`Plug'n'Play`](https://yarnpkg.com/features/pnp).
For this purpose new `env variable` was added to help to [load external extensions](https://yarnpkg.com/advanced/rulebook/#modules-shouldnt-hardcode-node_modules-paths-to-access-other-modules): `PUTOUT_YARN_PNP`.

So if you use package **eslint-config-hardcore** you should run **ESLint** this way:
Expand Down

0 comments on commit 320818a

Please sign in to comment.