Fresh install of n can't be used about n HOT 8 CLOSED

and it couldn't switch my active install

That sounds like an issue with node installed twice, likely once into /usr/bin (by some other process) and into /usr/local/bin by n. The version which is found depends on the order of directories in the PATH environment variable.

If you run n doctor it will check for this situation.

from n.

fixed by using the POSIX compliant version on the POSIX branch

from n.

What version of Bash are you using in the failing environment?

There is some interesting syntax on that line, so maybe a really old or really new version of Bash is complaining:

from n.

I'm using sh, not bash, that might be the issue here

from n.

The n script starts with a shebang interpreter directive to use bash:

So in theory you can use sh (or zsh et al) as your shell, but the n script is interpreted using bash.

What version of Bash are you using in the failing environment?

Assuming you have a bash available, what I meant was what version is it? For example, I see:

% bash --version 
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin21)
Copyright (C) 2007 Free Software Foundation, Inc.

from n.

Sadly no bash, it's a super barebones buildroot system i'm testing, I don't even have apt or curl which makes changing node versions...difficult. n comes to save the day, since I do have npm, but that syntax breaks on sh. #751 's changes fix this so I'm looking forward to it's merge or completion :)

from n.

Thanks for the info. A vote for the posix compatible version. :-)

from n.

(although it acted a little strange on my try, n's tui only saw the version it installed and not the one already present on the system, and it couldn't switch my active install)

from n.