Webpack / UglifyJS bundling process issue about react-element-to-jsx-string HOT 5 CLOSED

Apparently this package's usage has already been called out within stringify-object's issues as well

yeoman/stringify-object#36

from react-element-to-jsx-string.

have you tried uglify-es:
https://github.com/mishoo/UglifyJS2/tree/harmony
... supposed to handle uglifying es6+

from react-element-to-jsx-string.

I could perhaps use another minifier if I use the full control mode of storybook but at this time the minifier is baked in to their build target.

from react-element-to-jsx-string.

Hi @dptoot,

For now we do not target browser usage for this project. As you're not the first to open an issue on this subject (#90) maybe we should consider it?

@vvo What did you think about this?

In the main time, the response given on the #90 issue could apply for you

from react-element-to-jsx-string.

have you tried uglify-es:
mishoo/UglifyJS2@harmony
... supposed to handle uglifying es6+

This is the right answer to this current issue, you could maybe contribute to storybook default minifier and use uglify-es as stated here: https://github.com/mishoo/UglifyJS2#note

Other relevant links:
yeoman/stringify-object#35
storybookjs/storybook#1570
storybookjs/storybook#1668

I am sorry this happens but stringify-object may have take this decision (of not building anymore for ES5) a bit too early. OR uglifyjs may have waited too long to implement changes to support ES6.

Either way, you have solution to fix this I believe in the post you saw.

Thanks a lot for contributing here!

from react-element-to-jsx-string.