Skip to content
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

How to use sourcemaps from bower_components? #57

Open
DylanPiercey opened this issue Dec 10, 2014 · 1 comment
Open

How to use sourcemaps from bower_components? #57

DylanPiercey opened this issue Dec 10, 2014 · 1 comment

Comments

@DylanPiercey
Copy link

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
Copy link
Collaborator

sukima commented Dec 11, 2014

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants