Fix tooling for publishing automatically through CI

[ViktorQvarfordt]

Maybe use this https://www.npmjs.com/package/np

[AntonNiklasson]

What's our requirements here? How do you publish the packages today?

[AntonNiklasson]

I need access to the npm packages :)

[ViktorQvarfordt]

I’ve given you access to npmjs.com.

Right now packages are published by manually running ’npm run build’ followed by ’npm publish’. First you need ’npm login’. It would be cool if we have an automted way to publish by pushing a git version tag commit or so, that builds and publishes to npm and also makes a github release. Im not sure how to best structure this. We can take inspiration from hocuspocus that also use a monorepo for multiple packages

[AntonNiklasson]

I've been doing some research around this. I think we could put something relatively simple together with lerna. I just need to find some time to actually build it out. 🤗

[ViktorQvarfordt]

I would like to understand more about the tools in this space. Perhaps something like this is useful https://github.com/changesets/changesets that focus specifically on release cycle for multi-package-repos. Slate is using this.