nodejs / unofficial-builds

Unofficial binaries for Node.js
https://unofficial-builds.nodejs.org
257 stars 54 forks source link

Node build 22.7.0 is missing #151

Open antoineKorbit opened 2 months ago

antoineKorbit commented 2 months ago

Pyright library is using your platform to download nodejs for Linux x64, and it now fails, because the v22.7.0 build is missing.

How can we re-generate the build ?

Pyright output: ``` WARNING: there is a new pyright version available (v1.1.371 -> v1.1.377). Please install the new version or set PYRIGHT_PYTHON_FORCE_VERSION to `latest` * Install prebuilt node (22.7.0) .Failed to download from https://unofficial-builds.nodejs.org/download/release/v22.7.0/node-v22.7.0-linux-x64-musl.tar.gz .. ```
rvagg commented 2 months ago

It looks like your musl build was one of the only ones that actually made it. It's there now, maybe you weren't patient enough. The rest seem to have trouble.

For debugging these kinds of problems, you should start by checking out the build logs: https://unofficial-builds.nodejs.org/logs/202408221421-v22.7.0/

Seems like a python problem running configure, maybe something was upgraded in the configure script that needs a newer python? We might need upgraded recipes here to get a python match.

rvagg commented 2 months ago

Some work in https://github.com/nodejs/unofficial-builds/pull/152 to sort at least some of it out, but it seems that only two of the recipes are working now for 22.x, musl and glibc-217. The others may need work to get python updated.

If someone wants to help fix this, then dig through the recent logs to see the actual errors and work backward from there.

webdrakib commented 2 weeks ago

Resolving Pyright Node.js Download Issue

It looks like you're encountering an issue with the Pyright library trying to download a specific version of Node.js (v22.7.0) for Linux x64, which is currently unavailable. Here’s how you can resolve this issue:

Steps to Resolve the Issue

  1. Update Pyright: Since there’s a warning about a newer version of Pyright available (v1.1.377), updating it might help resolve dependency issues. You can do this by running:
       npm install -g pyright

or if you are using it via pip:

      pip install --upgrade pyright
  1. Set PYRIGHT_PYTHON_FORCE_VERSION: If you want to bypass the download of the specific Node.js version, you can set the environment variable PYRIGHT_PYTHON_FORCE_VERSION to latest. This can often allow Pyright to work with a different version of Node.js that might already be installed on your system.
    export PYRIGHT_PYTHON_FORCE_VERSION=latest
  1. Manually Install Node.js: If you need Node.js v22.7.0 specifically, and it's not available via the official source, you can install another version of Node.js manually. You can use a version manager like nvm to install a specific version of Node.js:
    nvm install 22.7.0

After installation, make sure to set it as the default version:

    nvm alias default 22.7.0

Use Node.js from the System Package Manager: If you don't specifically need Node.js v22.7.0, consider using the version available from your system’s package manager:

   sudo apt update
   sudo apt install nodejs

Regenerate the Build: If you still want to regenerate the build for Node.js v22.7.0, you would need to:

Clone the Node.js source code:

    git clone https://github.com/nodejs/node.git
    cd node
    git checkout v22.7.0

Then follow the build instructions in the Node.js repository. Generally, you would run:

   ./configure
   make
   sudo make install

Make sure you have the necessary dependencies for building Node.js from source.

Check Compatibility: After completing these steps, make sure Pyright works correctly with the installed version of Node.js. You can test it by running:

   pyright --version