Suggestion: herd isolate-node should make the new version available immediately.

[thomas-alrek]

If I'm in a project's directory and need to switch it to a specific node version e.g. 16 I do the following:

herd isolate-node 16

However (and to my surprise), the new version isn't available in the shell until I start a new session.

node -v
v21.7.2

herd isolate-node 16
The site is now using Node 16.
Found '/Users/thomas/Documents/Development/Herd/floyen2/.nvmrc' with version <16>
Now using node v16.20.2 (npm v8.19.4)

node -v
v21.7.2

zsh
node -v
v16.20.2

This confused me, and it took some time to figure out why my builds where failing.
So I would suggest that the node-isolate command should source the new node version in the path immediately, or inform the user that they need to do this, to avoid confusion.