Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No binaries found #1

Closed
wesleycoder opened this issue Jan 13, 2024 · 4 comments
Closed

No binaries found #1

wesleycoder opened this issue Jan 13, 2024 · 4 comments

Comments

@wesleycoder
Copy link

Sorry for bothering, I know this isn't the official fnm repo.
I came here from Schniz/issues/694 where this comment points to this repo.

I have this on my .zshrc:

# .zshrc
export FNM_HOME="$HOME/.local/share/fnm"
if [ ! -x $FNM_HOME ] >/dev/null; then
  curl -fsSL https://vanaware.github.io/fnm-alpine/install.sh | zsh -s -- --install-dir $FNM_HOME --skip-shell
fi

export PATH="$FNM_HOME:$PATH"
eval "`fnm env --use-on-cd --shell zsh --log-level=info`"
eval "`fnm completions --shell zsh`"

This is my shell output when trying to install.

$ fnm install 18.17.1
Installing Node v18.17.1 (x64)
error: Can't download the requested binary: v18.17.1 for x64 not found upstream.
You can `fnm ls-remote` to see available versions or try a different `--arch`.

Is there anything I may have set up wrong?
I'm trying to run fnm on alpine through wsl on windows.
It's a very sad use-case but I was hopeful to get some help if possible.
I can understand if this is out of your hands too.
Thanks in advance.

@Vinfall
Copy link

Vinfall commented Apr 11, 2024

From Schniz/fnm@master...vanaware:fnm-alpine:master, this fork should work.

However, your output said Installing Node v18.17.1 (x64), which means it's still requesting the x64 build instead of x64-musl. (This is based on the assumption that https://unofficial-builds.nodejs.org/download/release/v18.17.1/ exists but it does so anyway...)

You can try my fork https://github.com/Vinfall/fnm/actions/runs/8642269712/artifacts/1404008438, it's really simple, just three lines of change to bypass the hardcoded arch check, see Schniz@0562c9f.

@wesleycoder
Copy link
Author

Thanks for the follow up!
Also thanks for the good work!

I've switched my setup since I opened this issue, and nowadays this issue doesn't impact me anymore, so I'll be closing this issue for now.

I'll have some spare time this weekend to test the mentioned solution.
If I find any problems I'll come back here and reopen this issue or open a more appropriate one with better description if needed.

If everything goes well I may drop by here and leave a praise :)

@Vinfall
Copy link

Vinfall commented Apr 11, 2024

fnm is just a binary (instead of shell alias like nvm) so the test should be easy, just download the artifact, unzip and mv it to $FNM_DIR/fnm.

You should also set shell rc as mentioned here (since they are no longer hardcoded like this repo):

export FNM_NODE_DIST_MIRROR=https://unofficial-builds.nodejs.org/download/release
export FNM_ARCH=x64-musl

@Vinfall
Copy link

Vinfall commented May 29, 2024

FYI, the original repo has released v1.36.0 without the hardcoded arch check. You can use that instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants