generate bundle with a different targets

[prateekbh]

generate bundle with a different targets

[rickiesmooth]

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.

[ForsakenHarmony]

That's weird, you do get an additional bundle as the output though?

[prateekbh]

Expected behavior is exactly what you’re looking for .
we can use some help for a repro of the bug

[rickiesmooth]

After some digging I found the issue in my implementation, in my case I had multiple babel-loaders rules: one that only included application code and excluded node_modules and one that only included node_modules - which caused this issue with the babel-esm-plugin.

My workaround was removing my node_modules rule and doing everything with one babel-loader rule (which eventually was better anyway) so I just wanted to let you know and see if this is a usecase you want to support?
I really enjoyed reading the blogpost about making this module and tried out some fixes, but I couldn't solve this issue myself. Maybe if you'd give me some pointers (and want to support this use case) I can make a PR.

Here's the test case I made to help clarify the issue:

• config: https://github.com/rickiesmooth/babel-esm-plugin/blob/task/reproducible-example-of-issue-with-multiple-loaders/tests/es5-target/es5-target.test.js
• actual output: https://github.com/rickiesmooth/babel-esm-plugin/blob/task/reproducible-example-of-issue-with-multiple-loaders/tests/es5-target/fixtures/output.es6.js

[rickiesmooth]

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