Testing CJS/ESM; Using GitHub Actions #8
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexeyraspopov
force-pushed
the
chore/CI
branch
from
b275248 to
dd535df
Compare
denysovkos
approved these changes
Sep 27, 2021
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this PR we aim at supporting Node.js v6+. I've restructured some test files to have a single test suite which we can run 1) against both ESM and CJS version 2) using the range of Node.js v6-v16 versions (using every single LTS version). GitHub actions looks pretty fast so far, obviously due to low number of effort needed to run stuff. We can even skip
npm installpart, but let's keep it at least for now.