Remove compiled code from git repository

[wilgert]

I think compiled code should not be included in the git repository.
Instead, it should be generated during the build and published in the release.

See also: https://kentcdodds.com/blog/why-i-dont-commit-generated-files-to-master

[se-panfilov]

I see you points, cause indeed it makes code review a bit polluted, but let me think a bit about that, cause I have some concerns

[se-panfilov]

@wilgert Can you clarify what exactly you are suggesting?

Cause the guy in the article first created branches for each release (which is okeish), but then switched to unpkg (which is a bit not okay)

I do have some concerns:

• I'd like to start using GitHub Packages at some point along side with npm;
• I do really want to be sure that the code in the npm registry is absolutely the same as the code in github. Adding some 3rd party (such as unpkg) in the middle increase the level of vulnerability. This article explains my concerns: https://medium.com/hackernoon/im-harvesting-credit-card-numbers-and-passwords-from-your-site-here-s-how-9a8cb347c5b5
• I'm fearing a bit that it might add some complexity;

[wilgert]

I suggest that the compiled version is not committed to git but only generated during the build in Github Actions/ Travis/ CircleCI (I don't care which one).

• I think making this change should not hinder you in using GitHub packages
• If you publish the same package as a release on GitHub and a package on npm I think you have your second concern covered.
• I think you only need to add some paths to .gitignore and make sure a build is ran in a CI environment whenever you want to do a release.

[se-panfilov]

@wilgert Well, don't get me wrong - that's sounds reasonable. But that means we have to setup publish process somewhere on CI/GH Actions or whatever.

That's the thing to do. Cause atm I just make releases via cli