node_version allows ^ while fnm it doesn't

[davesnx]

Hola @Schniz 👋🏼

You already know that I love you and respect you, but here's a bug:

~ cat .node-version
^18.0.0

Results into

Can't find an installed Node version matching ^18.0.0.
Do you want to install it? answer [y/n]: y
error: The requested version is not installable: ^18.0.0

[Schniz]

I believe that can be fixed with #839

cc @amitdahan is it correct?

[Schniz]

just discussed with @amitdahan

looks like it resolves ^18.0.0 as an alias. We have a bunch of options to have:

• only allow aliases to be in the form of ^[A-Za-z_].*, I don't like it very much as it's a breaking change, but maybe this breaking change makes sense?
• if fnm use considers the user input as an alias, it won't suggest to install this version as it will never be able to install it. (That's not entirely correct because if you have a custom nodejs distribution site then you can have named versions.. not sure if that's gonna work as I haven't tested it 😇 )

[davesnx]

I'm unsure about the options you gave ^^

Why is considered an alias? or more precisely why an alias can't be resolved? I mean, I believe node-version allows @next lts.

Does it mean that we would need a crate with https://github.com/ehmicky/node-version-alias If we want to support it correctly?