jdx/mise · error

precompiled node archive not found (404)

Error message

precompiled node archive not found (404)

What it means

On Windows, core:node downloads a precompiled archive; if the fetch reports NotFound (HTTP 404), install fails with this message. There is no source-compilation path on Windows in this plugin, so a missing prebuilt archive is fatal.

Source

Thrown at src/plugins/core/node.rs:170

            }
        }
    }

    async fn install_windows(
        &self,
        ctx: &InstallContext,
        tv: &mut ToolVersion,
        opts: &BuildOpts,
    ) -> Result<()> {
        match self
            .fetch_binary(ctx, tv, opts, || self.extract_zip(opts, ctx))
            .await?
        {
            FetchOutcome::Downloaded => {
                warn_patches_not_applied();
                Ok(())
            }
            FetchOutcome::NotFound => bail!("precompiled node archive not found (404)"),
        }
    }

    async fn install_compiling(
        &self,
        ctx: &InstallContext,
        tv: &mut ToolVersion,
        opts: &BuildOpts,
    ) -> Result<()> {
        debug!("{:?}: we will fetch the source and compile", self);
        let tarball_name = &opts.source_tarball_name;
        if let Err(err) = self
            .fetch_tarball(
                ctx,
                tv,
                &opts.source_tarball_url,
                &opts.source_tarball_path,
                &opts.version,

View on GitHub (pinned to afd2eddd3a)

Solutions

1. Wait for / choose a Node version whose win-<arch> archive exists on nodejs.org/dist
2. Verify the exact version string (e.g. 20.11.1, not 20.11) exists on the dist server
3. Use a vfox/alternative node backend if you need a version Windows builds don't cover

Example fix

// before (.mise.toml)
[tools]
node = "22.0.0" // windows archive missing

// after
[tools]
node = "22.11.0" // windows prebuilt published

ver="22.11.0"
url="https://nodejs.org/dist/v${ver}/node-v${ver}-win-x64.zip"
curl -fsIL "$url" >/dev/null && echo OK || echo "no windows prebuilt for $ver"

When it happens

Trigger: `mise install node@<version>` on Windows where nodejs.org has no <version>/win-<arch> archive (e.g. brand-new release not yet published, or removed/odd version).

Common situations: Pinning a Node version released minutes ago before Windows artifacts appear; requesting an architecture (arm64 on older versions) with no Windows builds; typo in version string resolving to a non-existent dist folder.

Understand the failure class

Background: 'Could not be found', 'does not exist', 'not found in database': the resource-not-found family when an ID, slug, key, or URI lookup comes back empty — this error's family across 20 libraries.

Related errors

• Ruby engine '{}' is not supported on Windows. Only standard
• install from exe
• {message}\ncompilation is disabled
• precompiled node archive not found and compilation is disabl
• TEMP is too long to replace mise.exe safely ({len} UTF-16 co

AI-assisted analysis of jdx/mise@afd2eddd3a (2026-09-09). Data as JSON: /api/errors/7dd51db27391d5d6. Report an issue: GitHub.