search

eugeneware / debowerify

A browserify transform to enable the easy use of bower components in browserify client javascript projects. This can be used in conjunction with deamdify to require AMD components from bower as well.
493 stars 51 forks source link

How to use sourcemaps from bower_components? #57

Open DylanPiercey opened 9 years ago

DylanPiercey commented 9 years ago

Is there a way to include the sourcemaps from bower_components into the current bundle?

My dependencies have an external sourcemap (and are in bower), however it would be nice if I was able to have it's sourcemap carry over so that I could see the non-minified bower_component.

Perhaps this is the wrong place to ask this, but some direction would be awesome.

sukima commented 9 years ago

@DylanPiercey debowerify is meant to be used with browserify which constructs (transpiles?) multiple sources into one source file. It ∴ creates it's own source maps. The intent would be to have one bundle file with all the things. With this your build system would then minify / post process the output from browserify. It is silly to minify minified code so one should use debowerify to address sources in the bower_components that are not minified. By using the unminified sources the source maps produced by browserify should match correctly.