frolovdev/easymoney

RFC: add release candidates workflow for publishing packages

Closed this issue · 0 comments

Is your feature request related to a problem? Please describe.
The final packets are run through a large number of npm-packages, so there is absolutely no guarantee that the code that went through the chain rollup->ts->babel is working.

e.g.
There was a problem when a code with the new bigint standard run through babel was transpiled to the example below:

Source code

const a = 10n ** 10n;

Transpiled by babel

Math.pow(10n ** 10n)

// => Boom, error!!!

So we need to find a way to run the integration tests on the final package, to know for sure that the final distributive is OK.

Describe the solution you'd like
Create release candidates and run integration tests on the resulted code. If tests pass publish public production version

Additional context
The error described above is the real error, that I get in manual testing when we have dev version (below <1.0.0)