-
Notifications
You must be signed in to change notification settings - Fork 16
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
Applying tinyify to plotly.js crashes Node #13
Comments
I'm wondering if this is related to the fact that the module that plotly exports is already a browserified bundle (thus somehow ending up in an infinite loop causing the overflow), which was kind of complicated to get to work in the first place, see: |
Scrap the comment above, it also happens when applied to the non-prebundled version of plotly. |
Getting the same over here. Probably because my bundle is quite substantial. if (!b._options.fullPaths) {
if (opts.flat) {
// Output a flat bundle, without function wrappers for each module.
b.plugin(packFlat)
} else {
// Replace file paths in require() calls with module IDs.
b.plugin(collapser)
}
} Commenting the above or using browserify |
Ack. you can use |
Getting the following error with |
ow, it's possible that bundle-collapser doesn't support some new syntax.
in case you're using async functions or something. it should be updated.
|
I am using some async/await indeed. I'd say it is coming from https://github.com/browserify/browser-unpack/:
Latest acorn is |
This works now when using today's versions of Node, plotly, tinyify and browserify. |
I'm trying to optimize a bundle that contains the (rather hefty) plotly.js library.
When I pass
-p tinyify
to my bundling command it will hang for quite a while and then crash, printing the following:When I omit the plugin, I can bundle things just fine. I also can pipe the bundle through
uglifyjs --mangle
just fine.I created a repo with an example case here: https://github.com/m90/tinyify-crash
As for Node internals, I am running the following on Ubuntu 16:
The text was updated successfully, but these errors were encountered: