nikivdev/code · error

no dependency manifests found from {} up to {}

Error message

no dependency manifests found from {} up to {}

What it means

The dependency update flow scans from the current directory up to a computed search root looking for manifests (package.json, Cargo.toml, etc.). If none are found anywhere on that path, there is nothing to update and it bails listing both directories.

Source

Thrown at src/deps.rs:64

                .with_context(|| format!("failed to run {}", program))?;

            if !status.success() {
                bail!("dependency command failed");
            }
        }
    }

    Ok(())
}

fn run_update_with_context(opts: UpdateDepsOpts) -> Result<()> {
    let cwd = std::env::current_dir().context("failed to read current directory")?;
    let search_root = update_search_root(&cwd);
    let context = UpdateDetectContext { cwd, search_root };
    let plans = build_update_plans(&context, &opts)?;

    if plans.is_empty() {
        bail!(
            "no dependency manifests found from {} up to {}",
            context.cwd.display(),
            context.search_root.display()
        );
    }

    print_update_summary(&plans);
    if opts.dry_run {
        return Ok(());
    }

    if !opts.yes && !confirm_update_plan(&opts, &plans)? {
        println!("dependency update canceled");
        return Ok(());
    }

    run_update_plans(&plans)
}

View on GitHub (pinned to a747e741ae)

Solutions

1. cd into the project directory that contains package.json / Cargo.toml and rerun
2. Verify a supported manifest file exists in the repo
3. If the manifest sits above/below the detected search root, run from the correct level or adjust the search root

Example fix

// before
$ cd ~/projects/my-app/docs
$ flow deps update   # no manifests from docs up to ~/projects/my-app

// after
$ cd ~/projects/my-app   # contains package.json
$ flow deps update

// confirm a manifest exists before updating
find . -maxdepth 3 -name package.json -o -name Cargo.toml -o -name go.mod | grep -q . \
  || { echo "no dependency manifests in this tree"; exit 1; }

When it happens

Trigger: Running the deps update command in a directory tree with no package.json/Cargo.toml/go.mod between cwd and the search root (typically the repo root).

Common situations: Running in an empty scratch dir or docs folder; project uses an unsupported manifest (requirements.txt-only Python, pom.xml); manifests are in a sibling directory outside the search path.

Related errors

• jj workspace corrupted
• dependency command failed
• dependency action is not a package manager command
• invalid js update target
• dependency update command failed: {}

AI-assisted analysis of nikivdev/code@a747e741ae (2026-09-01). Data as JSON: /api/errors/a9c49dd1d2807faf. Report an issue: GitHub.