Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

generate bundle with a different targets

See original GitHub issue

In my babel config I configured my preset-env to target IE11 and higher, and when I added the babel-esm-plugin I thought it would create another bundle which targets esmodules regardless of the targets that are defined in the babel config (in my case IE11).

When I do a standalone build that targets esmodules the filesize is considerably smaller and preserves ES6 features like classes etc, but when I use the plugin with my babel config and inspect the ES6 bundle geneerated by this plugin it doesn’t preserve ES6 features.

Is this expected behavior or am I doing something wrong? If it’s unclear I could setup a test case to provide more information.

Issue Analytics

State:
Created 3 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

rickiesmoothcommented, Apr 6, 2020

thanks for your replies! Yes the .es6 file is getting generated, and while I was setting up my test case, I see that it does work as expected. For some reason in my project it isn’t…I’ll investigate some more.

0reactions

rickiesmoothcommented, May 4, 2020

@prateekbh please let me know if you need any more info