Can't download the requested binary, not found upstream

[idleberg]

Unfortunately, one of our projects still relies on Node v5.4.1. This version is listed when running fnm ls-remote. However, trying to install this version for Windows, I run into the following error:

Installing Node v5.4.1 (x86)
error: Can't download the requested binary: v5.4.1 for x86 not found upstream.
You can `fnm ls-remote` to see available versions or try a different `--arch`.

Installing the same version on macOS works fine.

I assume this could be related to the fact that old versions did not provide a zip download for Windows (compare v5 and v12). I take it the ls-remote doesn't have any logic to differentiate which Node versions are available for which platform and architecture.

Is there a solution for this? I'm afraid there isn't, although I'd love to see my edge user case solved. At the very least this issue provides a reference to this behaviour.

[idleberg]

More generally: How would you feel about a flag, that allows specifying a custom URL?

Example

fnm install 5.4.1 --from-source https://.../node-5.4.1-win.zip

This would be a potentially dangerous action, so it should be confirmed after displaying a warning.

[joglomedia]

More generally: How would you feel about a flag, that allows specifying a custom URL?

Example

fnm install 5.4.1 --from-source https://.../node-5.4.1-win.zip

This would be a potentially dangerous action, so it should be confirmed after displaying a warning.

Are there still many people using this very old version?

I saw that currently fnm already has option --node-dist-mirror which you can use it to change the node mirror.

fnm install 5.4.1 --node-dist-mirror https://blablabla.bla/dist

You should place your zip file under path-to-root-dir/dist/v5.4.1/