Switch to Yarn plug-and-play

[Borewit]

Reference: https://v3.yarnpkg.com/getting-started/migration#switching-to-plugnplay

[Borewit]

@minht11, looks like both @biomejs/biome and remark-cli are not pnp compliant.

[minht11]

@Borewit I have zero experience with yarn pnp, but by the looks of it it tries to lint those files. You can just ignore them in biome.jsonc files.ignore

"./.pnp.cjs",
"./.pnp.loader.mjs"

Tested locally.

[minht11]

Biome minor version can have new rules, additional fixes enabled between versions, they specifically recommend pinning its version to prevent unexpected breakage

[Borewit]

I think the version is already pinned using yarn, in yarn.lock.

Any update typically needs to pass CI, usually triggered via dependabot.

[minht11]

If you have already installed dependencies then yes, but if for example you clone new project ant run npm install it will attempt to download never dependencies matching range, not sure on how specifically yarn handles it, but in this case I think it's better to pin it.

[Borewit]

@Borewit I have zero experience with yarn pnp, but by the looks of it it tries to lint those files. You can just ignore them in biome.jsonc files.ignore

"./.pnp.cjs",
"./.pnp.loader.mjs"

Tested locally.

It is as if the configuration file is ignored when switching to pnp. You need to run yarn install to test this branch (peek-readable/node_modules should disappear).

[minht11]

The latest breakage is because you enabled formatter.enabled to true, you can either disable it or run yarn lint --fix

[Borewit]

Great, only remark-cli remaining