Patrick Martin

@sigurdle Were you going to submit a PR or did you want us to address this issue for you?

shouldn't we also have an action that runs dist upon a PR getting merged, also, i activated discussions so that we can keep the issues section dedicated to issues, and...

I don't mean publish on a pr getting merged, just dist, so that the repository contains the lastest build at all times.

The dist files are useful for people using non-npm based systems.

plus they allow people to test the latest build from the current source code.

@Jolg42 How do we go about getting this setup?

@yne fair enough, i'll do a PR that adds it to the .gitignore. My question was more on the github action for releasing to NPM & github releases.

@Connum said: > I think it's good to have the current state of the master available in the dist folder as a preview version for people who want to test...

> Due to breaking changes, we're currently on our way to a major version update. It'd be great to have advanced users test it before officially releasing it. That's what...

That's what I was suggesting the "releases" ending in -git-commit_hash would be.