pace-src screws up source mapping

[Kilowhisky]

tried setting my vendor and local source file to use the pace-src and then threw a debugger statement in my code. Chrome can't map the source and just throws the breakpoint in the app-start.js

[SeyZ]

Very difficult to debug but I have exactly the same problem. The source map screwed up when I use "pace-src" in my index.html.

[Fryie]

I have the same issue.

[benmurden]

After much debugging and removing of packages, I can confirm I found pace to be the source of this issue for me, too.

[cowboyd]

This was causing us to not have readable stack traces as well. We played around a little bit and were able to almost get there by adding a sourceURL=vendor.js and sourceURL={APPNAME}.js so that when pace evals the sources, it can associate a filename with them.

That said, we weren't able to get to a full solution, but it might be a line of further investigation for others interested.

http://www.html5rocks.com/en/tutorials/developertools/sourcemaps/#toc-sourceurl

[temecom]

I reverted the 'pace-src' script load to standard 'src' and my debugging ability returned (that is the source code mapped properly) AND ember-cli-pace is still working. Does this make any sense?

[Turbo87]

@temecom it isn't showing the loading animation during initial app load though

[elanclarkson]

+1 I too have this issue.

[joshsmith]

Hey folks. Going to try to look into this and see if I can reproduce and track down why this might be happening.

If someone is able to put up a repo with the minimum test case with steps to reproduce, that would be really helpful.