You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to debug into this a bit and found that the path of the dependency that causes this is something like that: ./node_modules/.pnpm/dependency@1.0.0. In the ./node_modules/.pnpm/dependency directory there is another node_modules directory and no package.json file. I believe that this is what causes this problem.
If not, is there a workaround or so? I could somehow check that this is the only result, but is it safe to assume that all dependencies were checked or is it possible that there are dependencies with wrong licenses that were skipped (e.g. by failing early)? Either way a mention in the docs would also be great. EDIT: I just checked with a more restrictive config, I still only get this one result, so it is not safe to assume that all dependencies were traversed.
I saw that there was a similar issue before, however this is closed and my issue persists with version 12.0.1.
When I use
ignorein my configuration, I get the following error:When I remove it, I don't really get an error, but an incorrect result:
I tried to debug into this a bit and found that the path of the dependency that causes this is something like that:
./node_modules/.pnpm/dependency@1.0.0. In the./node_modules/.pnpm/dependencydirectory there is anothernode_modulesdirectory and nopackage.jsonfile. I believe that this is what causes this problem.Now to my question(s):
I could somehow check that this is the only result, but is it safe to assume that all dependencies were checked or is it possible that there are dependencies with wrong licenses that were skipped (e.g. by failing early)? Either waya mention in the docs would also be great. EDIT: I just checked with a more restrictive config, I still only get this one result, so it is not safe to assume that all dependencies were traversed.