Switch to pnpm

[tiberiuichim]

Work for this exists here: https://github.com/plone/volto/pull/2557/

I don't know anymore the problem that those additional exports in the package.json solve. It will be interesting to see, as far as I remember Volto worked, together with project. I don't recall the status of the testing infrastructure.

[pnicolli]

I would be interested in understanding more about pnpm, like what are its additional features, which problems it solves for us and what are the downsides of using a new tool like this. Of course I will do some reading of my own asap as well, this comment is just to suggest some starting discussion points.

[tiberiuichim]

@pnicolli Here's some interesting pages: https://rushjs.io/pages/advanced/phantom_deps/ and https://rushjs.io/pages/advanced/npm_doppelgangers/

Basically when you switch to pnpm the first thing it forces you to do is to cleanup all those dependency problems, which I did in that PR. Second, it enables properly linking a Volto development checkout into a Volto project, so that you can work on things that affect only addons (right now we use yalc for that, and it's a 3 step process, including a restart, with pnpm it work seamlessly, even hot reloading). And last, my hope is that we can cleanup our testing story for addons: right now we need to run unit tests for addons from a docker container because of jest + yarn limitations.

[davisagli]

This is basically done:

• Volto core switched to pnpm earlier this year.
• Volto projects using pnpm can be generated using cookieplone.
• There is an experimental docker image using pnpm at https://github.com/kitconcept/plone-frontend/tree/newapproach