-
Notifications
You must be signed in to change notification settings - Fork 41
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
Coffeeify sourcemaps have absolute paths to original source #29
Comments
After looking into this further:
|
Is this still an issue as of 1.1.0? |
@PatrickKing ^, I'm also interested if this is still an issue. |
Gave my test application another run with coffeeify@1.1.0 and Firefox 37.0.2. Firefox still isn't resolving the sourcemap for bar.coffee (though commenters in this issue suggest that this might be fixed) Sources section of the sourcemap produced by Coffeeify still has that absolute path.
So, nothing has changed. |
I've pushed a fix to master (not on npm yet). Please test it and let me know if it solved your problems |
2.0.0 is on npm now, closing this. Let me know if you have any problems |
The sourcemaps generated by coffeeify have an absolute path to the original .coffee file, which breaks source loading.
I've made a sample app demonstrating the problem. After checking out:
... open index.html in a browser, and look at the javascript sources. Chrome actually will follow the absolute path to bar.coffee, but Firefox will fail to load the source.
The (base64 decoded) sources portion of the sourcemap looks like:
Manually changing the absolute path to just
bar.coffee
fixes the problem.The text was updated successfully, but these errors were encountered: