"shadowed by another binary of the same name" warning after `volta install node`

[xpe]

~> volta install node
success: installed and set node@24.11.1 (with npm@11.6.2) as default
   note: node is shadowed by another binary of the same name at /Users/asidie/.volta/bin/node. To ensure your commands work as expected, please move ~/.volta/bin to the start of your PATH.

Here is the line-wrapped version of the warning note for easier reading:

note: node is shadowed by another binary of the same name at /Users/asidie/.volta/bin/node. To ensure your commands work as expected, please move ~/.volta/bin to the start of your PATH.

Environment:

• macOS Sequoia 15.6.1
• terminal emulator: macOS Terminal.app
• nushell version 0.106.1
• a fresh installation of Volta 2.0.2

Parts of my config.nu that seem relevant for Volta:

# See https://www.nushell.sh/book/configuration.html

use std/util "path add"

# macOS stores expected paths in `/etc/paths`
$env.PATH = open /etc/paths | lines

# Cargo (Rust)
path add '~/.cargo/bin'

path add '~/bin'

# uv (Python package manager)
path add '~/.local/bin'

# Volta : manages Node.js and JavaScript tools
$env.VOLTA_HOME = '~/.volta'
path add $"($env.VOLTA_HOME)/bin"

Comments:

1. The warning shown above is unexpected to me, because there (presumably) was no previous node installed there.
2. The warning string makes me wonder if there is any confusion around ~ expansion.
3. Could this be nushell related?
4. I recognize I have not provided a water-tight start-to-finish replication. But this is an ok start.

Possibly relevant nushell differences:

• nu still expands ~ to the user's home directory
• nu uses $env.HOME instead of $HOME as is the case for POSIX shells
• nu uses $env.PATH and tracks this as a list of strings, manipulable via the path command