Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrading to Babel 7. #5129

Merged
merged 3 commits into from
Sep 21, 2018
Merged

Upgrading to Babel 7. #5129

merged 3 commits into from
Sep 21, 2018

Conversation

dennisoelkers
Copy link
Member

Description

Motivation and Context

This change is upgrading Babel to the most recent version. It involves bumping dependency versions and changing preset/plugin names. Due to stricter import checking, a minor issue with an import in the OutputList was noticed and fixed.

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@kmerz kmerz merged commit 3c4484c into master Sep 21, 2018
@kmerz kmerz deleted the upgrading-to-babel-7 branch September 21, 2018 12:39
dennisoelkers added a commit that referenced this pull request Sep 24, 2018
This reverts commit 3c4484c.

After merging it, we found out that dev/prod builds are not working
properly, as the `add-module-exports` plugin for babel does not seem to
properly add unscoped `module.exports`-like default exports that do not
require using `.default` scope when importing them via `require()`.
kmerz pushed a commit that referenced this pull request Sep 24, 2018
This reverts commit 3c4484c.

After merging it, we found out that dev/prod builds are not working
properly, as the `add-module-exports` plugin for babel does not seem to
properly add unscoped `module.exports`-like default exports that do not
require using `.default` scope when importing them via `require()`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants