Closed alert-debug closed 3 years ago
Thanks @alertme-edwin for reporting this! I've released a new version and this should be fixed now 👍🏻
Yup, that works. Thanks so much @jeemok!
I don't know if this means you now have more time to work on this amazing project, but I think I will create a separate issue about the \n
strangeness I'm seeing (as mentioned in discussion number 53), and maybe other people will be able to +1
it if they can reproduce it on their systems.
Also, I keep seeing discussions about false positives in npm audit
reports (e.g. issue 1138 in the chokidar repo, and a proposed RFC for npm called "audit assertions"), and that always reminds me how better-npm-audit
could greatly improve the npm ecosystem if it searched for .nsprc
files in dependencies. I know that requires a lot of careful thinking, though, so I don't want to rush you. Take all the time you need, and keep up the great work.
I recently upgraded to
npm@8.0.0
(andnodejs@v16.11.1
) and I'm getting the message:when running
npm run audit
. Presumably that's because theindex.js
file is actually at the top level of the package's directory tree, and not in alib
directory. The tool still seems to function, but hopefully this is an easy fix.