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

Allow user to specify that built output should not export core #169

Merged
merged 1 commit into from
Feb 4, 2016

Conversation

suchipi
Copy link
Contributor

@suchipi suchipi commented Feb 4, 2016

Adds an exportCore option to core-js-builder that defaults to true.
If set to false, the compiled output will not contain a UMD wrapper to export the core library.

In one of our projects, we're using core-js to polyfill native Promises, but the UMD wrapper here causes problems with our test runner (because we're using r.js in our test runner, and it doesn't support the anonymous define module format).

Because we're only relying on core-js to polyfill functionality into the global scope, the exported package is unneeded- so this option would allow us to not export anything.

@zloirock
Copy link
Owner

zloirock commented Feb 4, 2016

Ok, maybe it will be useful for someone else. Thanks!

zloirock added a commit that referenced this pull request Feb 4, 2016
Allow user to specify that built output should not export core
@zloirock zloirock merged commit b98a792 into zloirock:master Feb 4, 2016
@zloirock
Copy link
Owner

zloirock commented Feb 8, 2016

Renamed to umd and published in 2.1.

@suchipi
Copy link
Contributor Author

suchipi commented Feb 8, 2016

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants