Skip to content
This repository was archived by the owner on May 1, 2020. It is now read-only.

Can't debug in chrome with 0.0.37-2 #275

Closed
peterpeterparker opened this issue Oct 29, 2016 · 5 comments
Closed

Can't debug in chrome with 0.0.37-2 #275

peterpeterparker opened this issue Oct 29, 2016 · 5 comments
Assignees

Comments

@peterpeterparker
Copy link

Hey,

With version 0.0.36 I was able to debug in chrome.

Yesterday I install 0.0.37-2 (following #267) and now I notice that I'm not able anymore to debug in chrome.

Is that a bug or is there any new configuration required to enable that functionality?

Thx in advance for your feedback

@lordgreg
Copy link

Exactly the same issue here. I've updated app-scripts using latest flag because I was tired of waiting 10 seconds every time I've changed a file, so currently, I'm using 0.0.38, but... joy...

NO SOURCEMAPS.

👎

@danbucholtz
Copy link
Contributor

@lordgreg, @peterpeterparker,

Hmm. That is not the expected result. I'll investigate and publish a fix asap.

Thanks,
Dan

@danbucholtz danbucholtz self-assigned this Oct 31, 2016
@peterpeterparker
Copy link
Author

peterpeterparker commented Oct 31, 2016

Thx a lot in advance @danbucholtz

Just installed 0.0.38 same results...but also won't be surprised if I missed something...again

@danbucholtz
Copy link
Contributor

This is fixed in 0.0.39. I have another issue tracking the Typescript sourcemaps which will be out in 0.0.40.

Thanks,
Dan

@lordgreg
Copy link

lordgreg commented Nov 1, 2016

Thank you for the fix @danbucholtz.

So should the sources now be really visible under opening 232 sub-folders? :) Upon investigating, the sources are actually JS files compiled from TS. I'll be waiting for your another release you've mentioned above. 👍

image

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants