Closed gavacho closed 11 years ago
:+1:
I've verified that this doesn't break sourceMap support (tested in chrome) and doesn't cause IE to break because of sourceMap
Is anyone maintaining this project?
Recent Chrome dev channel builds have deprecated //@ sourceUrl=
in favor of //# sourceUrl=
. Any reason not to move this filter to that syntax?
It'd be good to know if IE supports //#
in addition to //@
Some additional info here: http://updates.html5rocks.com/2013/06/sourceMappingURL-and-sourceURL-syntax-changed
I think that IE does not support source maps of any kind yet.
IE definitely supports //@
. This issue was opened because minispade-produced sourcemaps were braking IE :)
Seeing as TypeScript supports them, I'd be surprised if IE doesn't, but it is Microsoft. You never know.
@gavacho right but IE uses //@
for conditional comments, not for source maps. @jedhunsaker the articles about TypeScript support all refer to Chrome :)
@lukemelia I think you're right. I think it looks like there's support because it has some special support for eval
'd code blocks.
"Hopefully either the Visual Studio or IE (or both) team also pick up Source Maps and add support for them too."
http://www.aaron-powell.com/posts/2012-10-03-typescript-source-maps.html
Moving this discussion to #68
This fixes an issue where minispade'd files don't work in IE8/9. The who what when where why's of it all are described here: http://www.trdev.co.uk/2011/05/17/ie-gotchas-using-the-coffeescript-plugin-for-requirejs/