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

Fix backward-compatibility of babel-preset-es2015 - fixes T7536 #3635

Merged
merged 1 commit into from
Aug 5, 2016

Conversation

loganfsmyth
Copy link
Member

No description provided.

Object.defineProperty(module.exports, "buildPreset", {
configurable: true,
writable: true,
enumerable: false,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably worth noting why this has to be non-enumerable, to avoid triggering the check for unknown options

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call.

@jayphelps
Copy link
Contributor

jayphelps commented Aug 5, 2016

For those coming here still trying to fix their builds, upgrade your babel-core to the latest to solve the issue; and/or any dep that includes babel-core like babel-cli, etc. This PR is about fixing the issue for people who don't upgrade their babel-core.

@loganfsmyth loganfsmyth merged commit af50e31 into babel:master Aug 5, 2016
@loganfsmyth loganfsmyth deleted the fix-back-compat branch August 5, 2016 04:06
@@ -4,7 +4,8 @@ var expect = require("chai").expect;

suite("es2015 preset", function () {
test("exposes a function", function () {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably inaccurate now :>

eventualbuddha added a commit that referenced this pull request Aug 5, 2016
Originally pointed out by @Kovensky in #3635 (comment).
hzoo pushed a commit that referenced this pull request Aug 5, 2016
Originally pointed out by @Kovensky in #3635 (comment).
@lock lock bot added the outdated A closed issue/PR that is archived due to age. Recommended to make a new issue label Oct 7, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated A closed issue/PR that is archived due to age. Recommended to make a new issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants