Packages from `nodePackages_latest` don't result in executables in $PATH.

[seanparsons]

Describe the bug

A shell including packages from nodePackages_latest like yarn or pnpm don't result in executables on the path the way nodePackages does.

Steps To Reproduce

Steps to reproduce the behavior:

1. Run nix-shell -p nodePackages_latest.yarn --run "yarn --version"

Expected behavior

I would expect to see the version number of yarn instead of /tmp/nix-shell-433770-0/rc: line 1: yarn: command not found.

Additional context

This works find if nix-shell -p nodePackages.yarn --run "yarn --version" is run instead.

I stumbled on this earlier but I'm not entirely certain if it's related: #142915

Notify maintainers

Apologies @marsam if you're not the most appropriate person to pull into this!

Metadata

[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.76, NixOS, 21.05.3990.372e59d2af7 (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.16`
 - channels(root): `"nixos-21.05.3990.372e59d2af7, nixos-hardware"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:

# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

[seanparsons]

I've also attempted this with a more bleeding edge version of nixpkgs and it still appears to be an issue.

[andersk]

This seems to be a node2nix issue. Cc @svanderburg.

[happysalada]

node2nix only supports node_16 on master, the version included in nixpkgs does not support it.
Perhaps we could do a bump to unstable for node2nix ?

[andersk]

node2nix master still has this issue.

[miuirussia]

node2nix master still has this issue.

confirm it

[CMCDragonkai]

Yes node2nix master has this issue: svanderburg/node2nix#293.

However I'm not sure if this has anything to do with the OP's problem.

This is because nixpkgs master isn't even using 1.10.0 or 1.11.0: svanderburg/node2nix#291 (comment)

It claims it's on 1.10.0, but the actual executable is still 1.9.0 when you check the version.

[andersk]

@CMCDragonkai I suspect your test on 1.9.0 was tainted by the fact that 1.9.0 did not support --nodejs-16 (svanderburg/node2nix@e73c616), and you didn’t notice because 1.9.0 also did not complain about invalid options (svanderburg/node2nix#272). If you account for this (--pkg-name nodejs-16_x), you’ll see that 1.9.0 is equally affected, matching the OP’s problem.