[Feature request] Yarn 2 support

[tiziodcaio]

Feature request

Description

At the moment yarn (not classic) it doesn't work with vuepress! Why?

[Mister-Hope]

Vuepress is requiring other plugins and themes, and obviously it can not know and pre-declare those you are using and add them to package.json before publishing.

So you can only use it in loose mode

[meteorlxy]

@Mister-Hope I'm not familiar with yarn v2. So maybe we could put a tip like pnpm?

https://github.com/vuepress/vuepress-next/blob/b220524f1534a1ada3b896854dba181e8ea36221/docs/guide/getting-started.md#L8-L10

[Mister-Hope]

If a plugin or theme author only requires the packages that is actually declaring all the deps, we may let it work if the theme you are using, is manually requiring all the plugins, and you are requiring the theme in config files. Only in that way can we lake it work under strict mode under yarn2 or pnpm.

But we encourage you to use strings to represent the plugin and theme you are using, in that way vuepress will require the module itself and it won't be able to work under strict mode.

Is this description clear enough for you?

[Mister-Hope]

I think he actually wants to work in strict mode, which won't extract node_modules, but directly read them through plug'in'play.

That do have a lot benefits including fast installing, modules bundle to git, flat structure and better performance (also less chance to damage or break node_modules folder)

@meteorlxy

I am not sure, but maybe we could support this if we require the actual package and pass in inteadof filling in a string.

[Mister-Hope]

Maybe we can consider to use :

{
  theme: require('vuepress-theme-xxx'),
  plugins: [require('vuepress-plugin-xxx'), {
    // options
   }]
}

to support this.

Webpack and many other project choose to support this because it do helps.

But if we decide to support it, the string support must be dropped in user config files.

[meteorlxy]

It's already supported for plugins.

Could not get the reason why we need to drop string support 🤔 . Users could just do not use string if they want to use yarn v2.

[Mister-Hope]

Try to read this @meteorlxy https://yarnpkg.com/features/pnp

pnpm is similiar.

Under this mode, a package could only visit the packages list in it's deps.

And here is a support table: https://yarnpkg.com/features/pnp#native-support

From your historical reply and comments, I bet you won't support this. @meteorlxy But you can still have a look at it.

[Mister-Hope]

Here is this content in pnpm:

[Mister-Hope]

It's already supported for plugins.

Could not get the reason why we need to drop string support 🤔 . Users could just do not use string if they want to use yarn v2.

I got you, this is not the mainly problem.

The actuall problem is that plugins and themes may need to declare packages like @vuepress/core @vuepress/client in it's deps.

Also, all the plugins and the themes do need to use require intead of strings to work becuase @vuepress/core don't have access to any theme and plugins. So these package should be required manually and passed to it.

[Mister-Hope]

i am not very familiar with it either because I only have some "demo" project running under this mode.

A lot of deps may actually missing some deps which they should declare. It's kind a historical problem in my opinion.

[meteorlxy]

It's more compilicated. We are using absolute file paths heavily, e.g. clientAppEnhanceFiles.

If you confirm that loose mode could work, we can put a tip in docs.

[Mister-Hope]

It's more compilicated. We are using absolute file paths heavily, e.g. clientAppEnhanceFiles.

If you confirm that loose mode could work, we can put a tip in docs.

Emm, yes it is compilicated. This is definitely not the thing we should focus now, but I still hope we can make it in todo list and try if we can support it in the future.

Losse mode will work. Because it's fully compatable with V1.

[tiziodcaio]

Can we open an issue called PNP support?