Feature Request: Whitelist some packages from node_modules about ndb

[serkanyersen]

it works!! 👍 Thanks!!

[alexkozy]

I will fix it by showing everything from node_modules. It is a little blocked by introducing better way to fs.watch for changes inside folders, current way does not support a lot of folders and unfortunately node_modules usually contains a lot.

[CyberPhoenix90]

Showing eveything from node_modules is not great in my opinion, in some projects that will mean showing thousands of files that aren't relevant to the person debugging.

[alexkozy]

I just published version (1.0.11) that should resolve this issue:

1. run ndb from folder with your project,
2. go to settings tabs, open node_modules tab, wait a little,
3. set Whitelist next to module that you would like to be able to debug,
4. restart ndb, you should get node_modules/dependency in navigator view, debugger will pause inside this dependency as usual.
   I am looking forward for your feedback. 😄

[serkanyersen]

@ak239 Thanks for the change. I've just tested this feature on some projects but I'm not sure if I could get it working properly.

On one project, I'm able to see the packages, but after whitelisting they don't show up on file tree.

on another project, it wouldn't even show the package list.

You can see the packages are installed on this project.

but overall, this is exactly what I wanted.

[alexkozy]

First bug most likely related to at sign and I can reproduce it locally, fix will be available soon.
To fetch list of dependencies we run npm ls --json inside folder where ndb was started. Could you confirm that when you run this command for second project it runs without errors?

[serkanyersen]

it seems to work, here is the end of the output

I'm guessing these extraneous: package errors are preventing you from parsing the output. Those error logs are definitely are in the stderr though, because they disappear when I run the command like this npm ls --json 2>/dev/null

[alexkozy]

Thanks a lot! It helped me detect the problem.

[alexkozy]

Please check out latest version (1.0.12). It contains fix for both problems.