You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think that this is needed, or at least I don't understand why it's needed.
The BABEL_8_BREAKING (+ STRIP_BABEL_8_FLAG) only affects the compiled files and not the source files. We run linting and type-checking on the source files, which are not affected by those two flags.
However, when linting we use @babel/eslint-parser and some ESLint plugins directly from our repo: even if the source files are not affected by BABEL_8_BREAKING, it's the linter itself that changes behavior between Babel 7 and Babel 8. For this reason, running make lint in Babel 8 tests is valuable because the ESLint behaviour might change.
This reasoning doesn't affect type checking: the type checker is the same when using Babel 7 and when using Babel 8, so (given that the src files are the same) it should produce the same result.
The BABEL_8_BREAKING flag does affect sources. For example we have removed t.Noop in Babel 8 so path.isNoop is not defined in packages/babel-traverse/src/path/generated/validators.ts. If path.isNoop() is used somewhere, it will pass in Babel 7 but fail in Babel 8.
This file contains hidden or 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
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
outdatedA closed issue/PR that is archived due to age. Recommended to make a new issuePR: Internal 🏠A type of pull request used for our changelog categories
5 participants
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.
Currently we only run
eslinton the Babel 8 build. In this PR we also enabletscheck. I will mark the PR ready to review when CI is green.