PNPM and Parcel

[fussel178]

Summary

This PR introduces changes in monorepo handling and the build pipeline.

Details

Due to multiple issues with npm in the past, we should switch to pnpm.
It has native monorepo support and convenient workspace linking and better dependency resolution and installation performance. Installed dependencies are isolated and only have access to their direct dependencies which prevents usage of invalid package versions. (the counterpart of hoisting)

Additionally we should also switch to Parcel as our main build tool. Rollup has served us good in the past, but Parcel supports our special monorepo support much better while less configuration setup is needed.
It plays very well with pnpm.
As a nice addition the compile times improve drastically.

To test these changes, you need to install pnpm first:

npm i -g pnpm@next-7

Then, clear your current build files:

npm run clean
rm -rf node_modules

And checkout:

git checkout chore/parcel-migration

To use the new tooling, take a look and the new contributing guidelines.

Some of the test tooling currently don't work due to package manager changes. (especially storybook)
They're working on support for pnpm.

Additional information

n/a

Related links

• Closes Move to PNPM #1374
• Closes Move to Parcel #1375

CLA

• I have signed the individual contributor's license agreement and sent it to the board of the WüSpace e. V. organization.

[jantischhoefer]

I viewed all the changes and only can approve the work. Good job.
Also the build time became a lot faster.