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

Support core-js@* #69

Merged

Conversation

SagiMedina
Copy link
Contributor

remove node_modules/core-js/ from transpile node_modules to support core-js@2

remove node_modules/core-js/ from transpile node_modules to support core-js@2
@SagiMedina SagiMedina changed the title Update webpack.js.js Support core-js@* Nov 12, 2019
@KidkArolis
Copy link
Owner

This looks good. I'm just wondering, how are you etting core-js@2 alias in your case?

I'm asking, because was wondering if the existing line of code should already take care of this?

if (filepath.startsWith(config.resolve.alias['core-js'])) return false

@SagiMedina
Copy link
Contributor Author

@KidkArolis You can see here #64

@KidkArolis
Copy link
Owner

OK, got it.

Basically, if some npm dependency (AntD) uses core-js directly, jetpack breaks it by aliasing to core-js@2. But if you delete that alias in jetpack.config.js, then build still breaks because of the babel loader config. With this PR - we always exclude core-js, even if the alias is removed.

@KidkArolis KidkArolis merged commit 8c4441d into KidkArolis:master Nov 13, 2019
@KidkArolis
Copy link
Owner

Released in 0.17.2. Thanks for the contribution. And sorry for slow (no) response to the original issue.

@SagiMedina
Copy link
Contributor Author

No worries :) Sorry for opening it before trying to fix it myself.

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.

None yet

2 participants