You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 4, 2021. It is now read-only.
All the other TypeScript output was correctly being run through Buble, but not this one excerpt.
I've worked around it by adding these lines to my tsconfig.json:
"noEmitHelpers": true,
"importHelpers": true,
...so TypeScript is importing its own helpers now, and the TypeScript helpers from rollup-plugin-typescript are being stripped by Rollup. But it seems like the way the "helpers" are being injected is preventing the helpers from being run through later plugins.
I'm doing this two step transpile (TypeScript creating ES6, Buble creating ES5) for better import behavior. I'm not sure if there's a better way where all of the Node imports still work as expected (and can include ES6 code from node_modules), but this is what I've come up with.
In any event, I've listed my workaround, and I'm not going to personally dig into this any more.
The text was updated successfully, but these errors were encountered:
I just had an issue where I was getting a crash on older browsers, and I traced it to this bit of code from the TypeScript helpers:
This is how the code looked in the final output, including the ES6
const
keyword, even though I was running the code through the rollup-buble-plugin:All the other TypeScript output was correctly being run through Buble, but not this one excerpt.
I've worked around it by adding these lines to my
tsconfig.json
:...so TypeScript is importing its own helpers now, and the TypeScript helpers from rollup-plugin-typescript are being stripped by Rollup. But it seems like the way the "helpers" are being injected is preventing the helpers from being run through later plugins.
I'm doing this two step transpile (TypeScript creating ES6, Buble creating ES5) for better import behavior. I'm not sure if there's a better way where all of the Node imports still work as expected (and can include ES6 code from node_modules), but this is what I've come up with.
In any event, I've listed my workaround, and I'm not going to personally dig into this any more.
The text was updated successfully, but these errors were encountered: