feat: support yarn pnp

[aparajita]

Version

v2.4.3

Reproduction link

#4875

Steps to reproduce

create-nuxt-app test
[select yarn as package manager]
cd test
rm -rf ./node_modules
yarn --pnp
yarn run dev

What is expected ?

I expect nuxt to run the dev server.

What is actually happening?

/bin/sh: nuxt: command not found
error Command failed with exit code 127.

Additional comments?

See #4875 (comment) for reference.

_{This bug report is available on Nuxt community (#c8642)}

[pi0]

The first issue found. PNP seems not supporting bin field as an object. (Only string supported) workaround for testing: yarn node -p "require('nuxt-edge/bin/nuxt')" (more issues exist) will update issue if found workarounds

[alexanderniebuhr]

Are there any updates on this? I really want to dive deep into Yarn Plug’n’Play.
Could you provide any workarounds for testing?

[aparajita]

Unfortunately until more people use modern package managers (that share a package store instead of copying every package over and over again into a flat hierarchy), this seems to be a non-issue for the maintainers. Please correct me @pi0 if I'm wrong.

If I understand correctly, the current stance is: module X depends on Y, and Y depends on Z, therefore X should be able to implicitly depend on Z. Unfortunately that is depending on an implementation detail of the current generation of package managers. And no package manager ever promised that dependencies are transitive in this way.

Honestly @pi0 I'm struggling to understand the reluctance to declare dependencies in the package in which they are required. Is it a philosophical thing? To say you want to modularize dependencies by pushing them up the module hierarchy doesn't quite make sense. No matter how many times you declare a dependency, if it's the same version, there will only be one copy installed, whether it's a flattened hierarchy or a shared store. So modularization of code !== modularization of dependencies.

[danielroe]

The bin bug identified by @pi0 appears to be fixed in yarn v2. (There are still undeclared dependencies within Nuxt.)

[pi0]

So modularization of code !== modularization of dependencies.

Yeah, I completely agree with you @aparajita. The concern was that we splitted @nuxt/vue-app and @nuxt/webpack to make nuxt framework/bundler agnostic in the future. Like also supporting parcel and rollup and also react, etc. Those users don't need these default packages to be installed.

BTW by the time, it seems that's not going to happen. Nuxt community and ecosystem are tightly coupled with both webpack and vue. I'll ensure this with core team and make a PR to add explicit dependencies.

[aparajita]

!@pi0 متشکرم

[danielroe]

Will be closed by #8389