In preparation for adding workspaces for web components and new docs we can benefit from introducing a streamlined and optimized way of running e.g. build, test and publish/deployment workflows, and use those for our current workspaces:
Included in this issue is also a quick pros/cons evaluation of NX and turborepo - but we should keep it short and get to using one or the other rather quickly to get experience actually using it.
Then we should set up building affected packages for all workspaces, and testing for core and designsystem.
Scope
It is out of scope to streamline publishing of packages and deployment tasks in this issue.
In preparation for adding workspaces for web components and new docs we can benefit from introducing a streamlined and optimized way of running e.g.
build,testand publish/deployment workflows, and use those for our current workspaces:libs/designsystem,libs/core,apps/cookbook,apps/flowsTech refinement
Included in this issue is also a quick pros/cons evaluation of NX and turborepo - but we should keep it short and get to using one or the other rather quickly to get experience actually using it.
Then we should set up building affected packages for all workspaces, and testing for core and designsystem.
Scope
It is out of scope to streamline publishing of packages and deployment tasks in this issue.