Feature Request: Handle TypeScript Better

Steps to reproduce

Tell us about your environment:

• ndb version: v1.0.6
• Platform / OS version: Ubuntu 16.04
• Node.js version: v8.10.0

What steps will reproduce the problem?

Please include code that reproduces the issue.

I followed this guide, hoping it would work out essentially the same. It _kind of _ works. I opened ndb with ndb . in the root of my project, then ran one of my npm scripts from the ndb UI. The script was ts-node src/index.ts (I had to move my typings around a bit before this would work), and it ran just fine from inside ndb. Unfortunately, after starting the script, I could not set breakpoints in any of the files listed by ndb. However, if I stopped the script, set a breakpoint in one of the .ts files (specifically, src/inxex.ts), then restarted the script, ndb would start up and open a new file. This file matches what the article linked above led me to expect - the tab says the file is index.ts?[sm]. However, I cannot actually select this or other files from the list of files presented in the UI by ndb.

At this point, with the already-opened index.ts?[sm] file, I can move the breakpoint around and it appears to work fine.

What is the expected result? If sourcemaps are available, the sourcemapped files should be available instead (or at least in addition to) the normal .ts files.

What happens instead? They are not listed in the UI.

[ak239]

Finally this one should be fixed in just published 1.0.20. Please check it out. 😄

[ankur123]

I am seeing the same issue as well