[ousamabenyounes]

Summary

• annotate successful, unfiltered nvm ls-remote output with named local aliases and the latest node alias, including aliases that resolve to node on an LTS row
• omit the obsolete built-in stable and unstable aliases and safely ignore malformed or non-printable alias names
• preserve filtered, LTS-only, and failed output, including when similarly named environment state exists
• add POSIX-shell regression coverage for colored and non-colored output

Test verification (RED → GREEN)

• RED before the review fix: bare nvm ls-remote did not annotate a named alias; got >v1.0.0 (LTS: Argon)<
• GREEN after the fix: the focused named-alias regression passes under sh, Bash, and Dash with GNU awk and mawk; the pinned-container zsh run also passes
• RED for the CI-discovered unload regression: function pollution found: > nvm_get_remote_aliases<
• GREEN after registering the helper for unload: the existing unload regression passes under sh, Bash, and Dash; reverting that line reproduces the RED result

Validation

• focused named-alias and unload regressions: sh, Bash, and Dash
• awk portability: GNU awk and mawk
• shell portability: pinned-container zsh
• ShellCheck: nvm.sh under Bash, sh, Dash, and ksh dialects
• EditorConfig lint and git diff --check

Fixes #2786.

[ljharb]

Please add examples of using named aliases as well, including when node is also an LTS version, or a local alias is.

Also, let's not include stable or unstable, since these are outdated built-in alias names.

[ousamabenyounes]

Addressed @ljharb's review: the latest line now shows (Latest: node, stable) — node is defined as the stable alias, so both built-ins are listed together while legacy unstable is omitted. Updated nvm.sh, the nvm ls-remote.txt mock, and the nvm ls-remote aliases unit test.

Verified locally RED→GREEN: the unit test fails on node alone and passes with the change (hermetic, no network); the mock matches the real output byte-for-byte apart from color codes. Also rebased onto master to drop the merge commit that was failing the Automatic Rebase check — it and all 36 fast/tests (slow) jobs are now green with 0 failures (the earlier install-latest-npm (18) self-signed-cert error was a transient flake, now passing).

Still open: PR remains a draft pending your go-ahead to mark it ready.

[ljharb]

made some tweaks, and added nvm_has_italics to master so we can use that styling for the aliases