The repo should not include `./dist` directory

While hacking into the code (npm run dev), every time the project is built, the ./dist files are generated. almost (not every) every master commit includes the ./dist/ files, and with every git pull I get conflicts in dist/. Some are because the master commits include functionality in src that have not been built and my local builds them

So I’m forced to cherry-pick my functionality without dist into a rebased clean master every time i need to pull. It’s a pain.

Also, i see PR from collaborators with dist folders that probably will cause huge conflicts when not fully rebased, and owners including dist folder with their PRs

If the dist is excluded and only generated when publishing (to npm, docker, whatever), dev history maybe is easier

[shockey]

Github releases can be created programmatically, so it’d be possible to add creating a zip and attaching that zip to the Github release to our build process.

[shockey]

Closing this, as we’ve since discontinued the modification of /dist/ outside of releases.