First stab at SourceMapDevToolPlugin exclude option - #897
Conversation
|
Please make it behave like the |
|
@sokra ha, I didn't know about these options, there is not much documentation for
|
There was a problem hiding this comment.
Could you move this into a separate file? So it's shared by UglifyJsPlugin and SourceMapDevToolPlugin. We don't want to have duplicate code.
There was a problem hiding this comment.
Done. Since one of them was already using ModuleFilenameHelpers and this helper seemed to deal with files already, that's where I moved these functions, but I could move them to yet another file if you suggest a name.
Yes please add them back. (Both plugins should share the same logic) |
Previously the SourceMapDevToolPlugin didn't use a options object. This was refactored latter. |
|
Alright, here you go, factorized code, which brings back |
|
Anything else you want me to add? |
No looks good... I'll merge it once I have some free time... |
|
Thanks, was just checking. Keep up the good work. |
First stab at SourceMapDevToolPlugin exclude option
|
Thanks |
per @gaearon suggestion, see issue #650 raised by @davidtheclark: "The problem with this is that the vendor file can get pretty big, and its gigantic sourcemap then severely slows down dev tool initialization on page reload. I would much prefer to only have a sourcemap for my app chunk (and not to have a sourcemap for my vendor chunk)."
This is a first stab at the corresponding
excludeoptions.Note that it might get tedious to have to explicitly instantiate
SourceMapDevToolPlugin, maybe a more global option suchas output.sourceMapExcludeChunkscould be introduced as well.