Dave Geddes

+1 as someone using webpack, I have no idea where the actual errors are without source map support.

For anyone else needing this, I've found that adding `?catch=false` to the URL at least lets the errors make it to the console so the browser can use source maps...

This issue still makes using jasmine such a major pain when using something like webpack. Not knowing what line errors are coming from makes things impossible.

I need this as well. For my use case I'm emulating locally my server's proxy settings. Hoping something like this would work: ```js "rewrites": [ { "source": "/game/main", "destination": "http://localhost:9000/main"}...

Can you share the grunt tasks you're running when you do this? Are you running the `watch` task right after? `$ grunt karma:unit watch` should work for example.

Gotcha. Haven't tried it combined with the singleRun option, as it was mostly for development/watch mode. Try moving regarde to the end, that may do it. Curious though, it looks...

Did moving regarde to the end do the trick?

Strange, it's working for others w spawn. Can you boil it down to a simple example and send it to me? I'd be happy to take a closer look.

> I had the same port and runnerPort specified in my "broken" app @Iristyle can you verify if that's the cause for yours? Also, which version of karma are you...

@abierbaum thanks for putting a sample together, I'll take a look.