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

Source maps broken when using with coffee-script 1.11.* #41

Closed
tad-lispy opened this issue Nov 3, 2016 · 1 comment
Closed

Source maps broken when using with coffee-script 1.11.* #41

tad-lispy opened this issue Nov 3, 2016 · 1 comment

Comments

@tad-lispy
Copy link

When using with coffee-script 1.11.0 or 1.11.1 (latest at the time of reporting) this command:

browserify --debug --transform coffeeify --extension .coffee --outfile build/application.js src/index.coffee

produces a bundle with source maps that make Chrome Dev Tools display files with .coffee extensions, but compiled JS content, whit source maps string at the bottom:

screen shot 2016-11-03 at 14 01 34

It might be related to change in lexer and parser announced in the changelog for v. 1.11.0:

Improved the internal representation of a CoffeeScript program. This is only noticeable to tools that use CoffeeScript.tokens or CoffeeScript.nodes. Such tools need to update to take account for changed or added tokens and nodes.

I don't think it's a bug in CS, as the source maps are generated correctly if I do it like that:

coffee -cMo build/js/ src/
browserify --debug --outfile build/application.js build/js/index.js
@jnordberg
Copy link
Owner

Published as 2.1.0

Let me know if there is any problems

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