Use the new sourceMappingURL syntax.

[russelldavis]

(See http://updates.html5rocks.com/2013/06/sourceMappingURL-and-sourceURL-syntax-changed)

[edc]

Thanks for sending this in.

[ashmoran]

I'm new to source maps so I've just been hacking away trying to get a build pipeline working. One thing I noticed is that the mapcat on npmjs.org is behind the GitHub source, so initially I installed in with npm from a cloned git repo.

After a while I discovered that Chrome wouldn't load my source maps regardless of the path in them, at which point I started Googling and discovered that this is Chrome's fault:

brunch/brunch#599

If it's true that "Chrome 29 will not land for at least 2 months", pushing this commit to npmjs.org may mysteriously break source maps for people using mapcat with Chrome. I don't know what the solution is, but I thought I should warn you about what I ran into.

[edc]

@ashmoran Thanks for the info. I will probably push the HEAD commit to npm after Chrome 29 then.