Versioned dependencies (via `--dep`) are not found

Open

#136 opened on Jul 29, 2024 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: rust
Domain: cli, tooling

Research direction

Reproduce the issue with aaugh.wac and the two wac resolve commands, comparing versioned and unversioned --dep values. Trace the dependency-resolution and error-reporting entry points to determine whether versioned dependencies are supported; done means either the versioned dependency resolves or the error clearly explains the required syntax or limitation.

Written by the indexing model from the issue text.

Description

I have the following WAC document:

package root:component-val@0.0.1 targets fermyon:spin/http-trigger@2.0.0;

let c = new root:component { ... };

export c...;

I resolve it like so:

wac resolve aaugh.wac --registry wa.dev --dep "root:component=./target/wasm32-wasi/release/calculator_spin.wasm"

And life is good. But if I change root:component to have a version:

package root:component-val@0.0.1 targets fermyon:spin/http-trigger@2.0.0;

let c = new root:component@0.0.1 { ... };

export c...;

and invoke with the version:

wac resolve aaugh.wac --registry wa.dev --dep "root:component@0.0.1=./target/wasm32-wasi/release/calculator_spin.wasm"

I get:

error: failed to resolve document

  × package `root:component` does not exist in the registry
   ╭─[aaugh.wac:3:13]
 2 │ 
 3 │ let c = new root:component@0.0.1 { ... };
   ·             ──────────┬─────────
   ·                       ╰── package `root:component` does not exist
 4 │ 
   ╰────

(If I revert the command line to the unversioned, uh, version, same error.)

Is this behaviour intentional? If so, could the error indicate more specifically what the user should do to fix it?

Dominant language: Rust
Stars: 208
Forks: 41
Avg merge: 2d 7h
Merged PRs (30d): 3

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[coverage-improver] Cover empty-artifact fallback root in build_plugin_plans Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

TheLarkInn/aipm#2413 · Opened Sep 24, 2026
AGENTS.md points to src/settings_window.rs, src/config.rs, and src/app.rs, which were split into directories Open

documentation

Difficulty 1/5 Under an hour Newbie friendliness 90/100

alexgorbatchev/simple-ptt#15 · Opened Sep 24, 2026
bench: run.sh's skip-update message always cites bench/skips.txt Open

tooling

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

svandragt/vivace#313 · Opened Sep 24, 2026
`t/vm/frames/light-call-frame-writes-dedup.t` wall-clock ratio check fails under `-j4` load Open

todo:ticket

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

tokuhirom/mutsu#9299 · Opened Sep 24, 2026
fix(taiko-client-rs): prevent BeaconClient panic on zero beacon spec values Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

taikoxyz/taiko-mono#22168 · 1 comment · Opened Sep 24, 2026

More Rust issues