Update @babel/core: 7.8.3 → 7.8.4 (patch) #6
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @babel/core (7.8.3 → 7.8.4) · Repo · Changelog
Release Notes
7.8.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 34 commits:
v7.8.4
[@babel/cli] Copy ignored files by default (#11063)
Fix core-js 2 builtin data for opera (#11066)
feat: support node 6 for levenary (#11059)
Update compat table (#11039)
Avoid compiling the _typeof helper with itself (#11049)
Update browserslist (#11058)
Update failing tests after last merged PR
Delete duplicated file in `@babel/compat-data` (#11041)
chore: map mobile browser data to their desktop version (#10814)
Update preset-env fixtures (#11040)
polish: throw human-friendly error when item-option pair is in… (#10969)
refactor: simplify toAssignable routine (#11032)
fix(babel-parser): avoid state.clone() to clone the whole token store (#11029)
Fix missing ClassDeclaration references after scope#crawl (#11011)
Check that generated compat-data is up to date on CI (#11024)
update compat-data related docs/config [skip ci] (#11030)
Enable `no-process-exit` ESLint rule (#11025)
fix: properly parse member expression after property initializ… (#11031)
Fix rest parameters indexing with TypeScript 'this parameter' (#9714)
add AST for the module attribute proposal (#11015)
Update coalesce precedence (#11017)
chore: use @babel/eslint-config-internal (#11026)
chore: replace yarn-upgrade by bump-babel-dependencies in e2e tests (#11021)
fix: for-of transform should skip for-await-of (#11023)
Re-generate preset-env fixtures (#11016)
fix: triple __proto__ in object patterns should be allowed (#11009)
Re-generate plugins compat data
Exclude `import()` tests from pubilsh build (#10995)
Fix parentheses removal in nullish-coalescing operation (#11014)
fix: supply ‘.’ subpath for node.js < 13.2 (#11006)
Duplicate `__proto__` key should be allowed in object patterns (#10987)
chore: test against babel-preset-app (#11004)
Add v7.8.3 to CHANGELOG.md [skip ci]
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
depfu/
.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands