Sourcemap support #259

Closed
martinheidegger opened this Issue Dec 26, 2012 · 5 comments

Projects

None yet

4 participants

@martinheidegger

It would be awesome if browserify could create source-maps for the generated files.

@substack
Owner

You can do --debug which is nearly as good. It uses // @sourceURL instead of full source maps.

@substack substack closed this Feb 22, 2013
@substack substack reopened this Feb 22, 2013
@michaelficarra

@martinheidegger: I have a new project, commonjs-everywhere, which provides similar functionality to that of browserify, but with full source map support. That might be a suitable replacement for you.

@martinheidegger

@michaelficarra Have to check it out, thank's for the link!

@substack
Owner

--debug is back with a vengence in 2.5 and uses inline base64-encoded sourceContentsURLs so you can have transforms with local inline source maps that will get parsed and offset into the global bundle offsets. Just use a browser that supports sourceContentURLs (like chrome >= 25)

@substack substack closed this Mar 12, 2013
@jiyinyiyong

"replacement", really?

@jiyinyiyong jiyinyiyong referenced this issue in coffee-js/languages Apr 1, 2013
Closed

Browserify + coffeeify 的前端调试方案 #55

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment