global pnpm check 'no dependencies'

[ekwoka]

When running ncu -gp pnpm it finds no dependencies. This started, as far as I can tell only in the last day or two.

Could this be related to the updates in pnpm 8? As you can see, it seems to have no found updates to even see that ncu is updated (manually updating that one did not fix it)

ncu -g still works fine.

[raineorshine]

Oops! That must be a regression. Thanks for letting me know. I will look into it.

[raineorshine]

Here's what happened: Commit 09c9680 added the ability to override boolean options in the cli, e.g. --peer false. Unfortunately this broke the use of combining boolean short flags.

I have reverted the offending commit and added tests to prevent this from happening again. Published in v16.10.3.

[ekwoka]

Confirmed, works :D

[diegocr]

ncu -g still works fine.

By any chance fixing this for pnpm broke using ncu -g ? because it's no longer working for me, been a while this way and patiently waiting for it to be fixed, but since it hasn't happened yet just thought on commenting here about it :)

Edit: i am now realizing all that was made to fix this was reverting a commit, so... must not be related, dunno if there were some other commits at the time that may broke this, or if it's something tied to my system... i.e. win11, nodejs installed on a non-C drive, dunno what other troubleshooting details i can provide, lmk.

[raineorshine]

@diegocr It's not related to this issue, but it is possible there was a different regression. It's going to be tough to identify without a minimum reproduction case, but if you open a new issue I can provide some troubleshooting tips.

[diegocr]

Thanks for the prompt response.

Just thought about running ncu --verbose -g and found where the problem is, there i do see a options.prefix pointing to %APPDATA%\npm but that path here doesn't exists (because nodejs is not installed on the system drive, as pointed)

I made a symlink and got ncu -g working again, but... perhaps ncu should be using the NODE_PATH environment variable for this "prefix" value (?)

fwiw, on ~/.npmrc i do have:

prefix=D:\\nodejs
cache=R:\Temp\npm-cache

and NODE_PATH does point to D:\nodejs\node_modules (the before mentioned symlink does point to this path)

PS: Could still file a new ticket/issue if you think it's still needed ;)

[raineorshine]

@diegocr Thanks! That's very informative.

Yes, if you could create a new ticket with that information we can track it there. I will think if there could be any regressions, but it makes sense to use NODE_PATH if it exists.

[diegocr]

Here you go: #1315

Cheers :)