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
Transform generateRawBundles such that any bundles (that are generated with a source map) have the path to the source-map appended as a comment at the end of the generated source.
It may be worth splitting the code generation piece out into a separate pluggable, so that it is easier to override when a map is returned. If that is the direction that is taken, that new pluggable should be transformed instead of generateRawBundles.
The plugin itself should probably take a config format, so that the path can be customized. This could use string-pattern replacement, regex, or whatever provides the cleanest API.
The text was updated successfully, but these errors were encountered:
It is probably worth adding this as default functionality, and exposing the sourceMappingURL path generation as a pluggable. As it is, source-maps are generated but they're not consumed by the browser because sourceMappingURL is missing from the end of the file. Exposing it as a pluggable will make it easy for users to setup custom mappings to accommodate their use-case.
Transform
generateRawBundles
such that any bundles (that are generated with a source map) have the path to the source-map appended as a comment at the end of the generated source.It will look something like this:
It may be worth splitting the code generation piece out into a separate pluggable, so that it is easier to override when a
map
is returned. If that is the direction that is taken, that new pluggable should be transformed instead ofgenerateRawBundles
.The plugin itself should probably take a config format, so that the path can be customized. This could use string-pattern replacement, regex, or whatever provides the cleanest API.
The text was updated successfully, but these errors were encountered: