-
-
Notifications
You must be signed in to change notification settings - Fork 586
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
Not working as an output plugin (warnings printed) #858
Comments
Please see https://www.rollupjs.org/guide/en/#using-output-plugins. Neither plugin is intended to be used as an output plugin. |
Thank you. This was the issue I meant to link to above, and the related PR. They certainly give the impression it was meant to work. Are you saying that it's not possible to generate two outputs from the same input, one that runs through Babel and one that doesn't? |
I see there is a I guess ideally, the warning in the first place might say something like
|
Thanks for confirming. It might be worth submitting a modification request to the main rollup project ( |
Expected Behavior
Able to specify babel for certain outputs but not all.
Actual Behavior
Many warnings printed:
Additional Information
I'm actually pretty new to this stuff, so this could well be user error. However, my understanding was this was supposed to work as of v5: #360
My actual project (from which the minimal repro is derived) is here. My goal (possibly misguided) was to provided a non-babel ES5 version of the library for modern consumers, and a legacy UMD+babel version for use in script tags, and in Node (for testing with Jest).
I did note this advice:
But I didn't know how to make that work in the case where
commonjs
is applied for all inputs, butbabel
is not.The text was updated successfully, but these errors were encountered: