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 Dec 5, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 5, 2019. It is now read-only.
Please upgrade source-map to 0.7.2 to get speed improvements #248
@andreicristianpetcu it is breaking change and break plugin on node@6 (eaking change: Drop support for Node < 8. If you want to support older versions of node, please use v0.6 or below.). We can't do this right now
@evilebottnawi Any chance we can get this released behind an opt-in flag.
My teamis having some production issues related to #272 e.g. out of memory and long build times. As I think we have determined, it's most likely due to a combination of unoptimized code in uglifyJS but also the cost of making source-maps. While there is nothing we can really do about the uglify js code, at least improving the source-map generation might help with that issue.
Activity
alexander-akait commentedon Mar 5, 2018
@andreicristianpetcu it is breaking change and break plugin on node@6 (eaking change: Drop support for Node < 8. If you want to support older versions of node, please use v0.6 or below.). We can't do this right now
mlavina commentedon Aug 6, 2018
@evilebottnawi Any chance we can get this released behind an opt-in flag.
My teamis having some production issues related to #272 e.g. out of memory and long build times. As I think we have determined, it's most likely due to a combination of unoptimized code in uglifyJS but also the cost of making source-maps. While there is nothing we can really do about the uglify js code, at least improving the source-map generation might help with that issue.
alexander-akait commentedon Aug 7, 2018
@mlavina it is not easy, because it is require
nodejs@8version minimum, but if you have ideas how we can fix it, PR welcomemlavina commentedon Aug 27, 2018
@evilebottnawi I will try to get a solution as soon as I can, but that might be a while to be honest.
However, a quick source-map gain that we might gain is if we can get this PR webpack/webpack-sources#23 merged for webpack-sources
Especially since in #272 we saw that
source-mapswere part of the problem.