Monorepo or PNPM

[Anthony Fu]

Currently, each folder have their own yarn.lock - docs/ demo/ which makes the packages separate and time consuming to install and maintain. Thinking of using one of the following solution

• Use yarn workspaces, which we will need to overhaul the project structure as yarn does not allow to have root package.json to be a public project. Which also make the scripts of releasing a bit harder (might need to introduce lerna?)
• Switch to pnpm, as pnpm allows to have root package.json to be the main package. It also provide pnpm -r run [script] and pnpm -r publish to manage the packages without extra dependencies.

/cc @pi0

[Pooya Parsa]

• Yarn is standard package manager we use for maintaining nuxt repos
• Docs intentionally has it's own yarn lock so for docs deployment we don't install module dev dependencies like jest
• Examples, Demos and Fixtures should use top level dev dependencies
• I also rather to use same tooling (standard-version for now) for doing releases

[Anthony Fu]

Yeah I don't really mind docs/, but demo/ also has its own package.json / yarn.lock which I found trouble testing the package. Or should I use test/fixture to test?

[Pooya Parsa]

lockfile in demo is like wise for codesandbox link when forking to only instal nuxt and nuxt-vite. Renovate bot should automatically update all lock files ☺️ For testing, yes you can use fixture or yarn dev that depends on top level dependencies and development code of module.