Clement Yan

> Is there any way to avoid duplicating identical dependencies? `peerDependency` is *the* way to do that. It is the only thing that tell package managers to enforce using the...

The settings docs does not show default values but rather an example value Otherwise some settings like `httpProxy` and `npmPublishRegistry` would be undocumentable

AFAIK that's just the PnP manifest as a JSON string inlined in the hook, right? So this is more about spec-ing how the PnP hook code is laid out? Alternatively,...

Wouldn't it make more sense to move in the opposite direction? I think it is much better to move both esbuild and pnp-rs to the out-line format as the primary...

> That's true to some extent but, in the case of Rust, the `pnp-rs` crate (which [we maintain](https://github.com/yarnpkg/pnp-rs)) is the ideal way to consume the data, as the maintenance of...

The information you provided is not nearly enough to reproduce the issue (for one it doesn't even include a `typescript` dependency). We use React with TypeScript and PnP is this...

As noted in the error message, `recompose@npm:react-recompose` means the `recompose` package at the version dist-tagged `react-recompose`. If you want to install the `react-recompose` package under the alias `recompose`, you want...

I think Biome's VSCode plugin supports PnP out-of-the-box? Or are you integrating with a different editor?

Hmm... I just tested on VSCode 1.102.0-indsiders and Biome VSCode Extension 3.1.0 and it works OOTB: 1. `yarn init && yarn add --dev @biomejs/biome` 2. Restart Extension Host 3. Create...

> Do you think it could be worthwhile to salvage the base integration for other editors? Should be fine. I don't use biome so I don't have a strong opinion...