That's understandable but very disappointing. Yarn PnP may not provide the best DX for development, but allows to speed up CI jobs dramatically by avoiding unnecessary I/O (I've seen 20+ seconds saved on each job just by turning on PnP!) and is the easiest way to catch bugs in declared dependencies.

Open in StackBlitz

pnpm add https://pkg.pr.new/@vitejs/plugin-legacy@21906 -D

npm i https://pkg.pr.new/@vitejs/plugin-legacy@21906 -D

yarn add https://pkg.pr.new/@vitejs/plugin-legacy@21906.tgz -D

pnpm add https://pkg.pr.new/vite@21906 -D

npm i https://pkg.pr.new/vite@21906 -D

yarn add https://pkg.pr.new/vite@21906.tgz -D

commit: 833b407

I propose we take a plugin approach if this is feasible? e.g. vite-plugin-pnp ?

Please consider adding a flag to make this warning skippable. I already have an unskippable warning from storybook telling me to stop using Yarn PnP.

As the author of the linked bug (and many others in vite, vitest and storybook relating to pnp support) I'm more than willing to take the risk locally of using PnP, so these warnings are quite annoying noise.

In terms of supporting yarn in vite, I've found that a very trivial plugin to intercept vite:resolve has fixed almost all the compatibility issues I've had personally, and I'd be happy to try and turn that into a published package. I did ask a while back about the possibility of making the vite:resolve plugin a bit more hookable, as currently monkey-patching core plugins is a bit of a pain.

There is somewhat support for PnP in Rolldown: rolldown/rolldown#5147

But with the issues here: #21875 and in rolldown: #21875, what is the bundler ecosystem at play is here?

If support of PnP is not something the teams want to manage, then would it been better to migrate existing support to a external project/plugin (e.g. rolldown) over a warning?

You can suppress the warning by using the customLogger option.

Just in case, this PR won't block you from creating a plugin that supports yarn pnp. That plugin can also suppress the warning internally. That said, we cannot provide a dedicated API to hook into the internals of Vite for that plugin as that would be the same with maintaining the dedicated code path.

That's sad indeed. No shame on maintainer team, I totally understand the burden.

But JS ecosystem is built on belief that everything's unlimited: bandwidth, disk space, I/O, and sometimes CPU. Since the goal of Vite is speed by efficiency (and thanks a LOT for rolldown), supporting PnP should be a main target: it just avoid wasting 600MB for nothing on each CI job.

@Glandos FYI nodeLinker: pnpm has a similar benefit with nodeLinker: pnp.

Here is the code to put in vite.config.ts:

const logger = createLogger()
const loggerWarnOnce = logger.warnOnce
logger.warnOnce = (msg, options) => {
  if (msg.includes('Using Yarn PnP with Vite is discouraged and PnP-specific bugs will no longer be actively worked on.')) {
    return
  }
  loggerWarnOnce(msg, options)
}

export default defineConfig({
  customLogger: logger,
}