Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Quick Start: wasm-pack prerequisite link returns 404

Aperta Adatta ai principianti
#303 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
85/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Ambito
documentation

Direzione di ricerca

Modifica documentation/develop/quick-start.md, dove il collegamento al prerequisito wasm-pack compare intorno alle righe 222–231. Trova istruzioni di installazione di wasm-pack mantenute e aggiorna il collegamento; verifica che una richiesta GET all’URL collegato restituisca 200. I criteri di accettazione sono soddisfatti quando il collegamento funziona e la verifica GET ha esito positivo.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug documentation

User impact

Readers installing the Rust prerequisites for the TypeScript SDK are sent to a wasm-pack installation-doc link that returns HTTP 404. They lose the linked platform-specific installation guidance, especially when the page's provided installer command does not fit their environment. The separate installer command shown on the page still responds, so this is a broken help link rather than a broken command.

Affected documentation and ownership

Observed versus expected

The page links:

[rust](https://www.rust-lang.org/tools/install) and [wasm-pack](https://rustwasm.github.io/wasm-pack/installer/) are leveraged to build and use the AnonCreds and DIDComm Rust libraries within TypeScript.

https://rustwasm.github.io/wasm-pack/installer/ returns HTTP 404 with a 404 page body and no redirect, on both observations. Expected: the linked wasm-pack installation guidance resolves to a maintained page, so readers can consult it when the shown commands do not work for their platform.

Distinguish this from the command on the same page:

  • https://rustwasm.github.io/wasm-pack/installer/init.sh → 200. The page's installer command is not claimed to be broken, and it was not executed.

Evidence and reproduction

Bounded public GET probes only, 10-second timeout, 2 attempts, 2026-10-29T16:58:25Z and 16:58:48Z:

GET https://rustwasm.github.io/wasm-pack/installer/
-> 404 (both attempts; served 404 page)
GET https://rustwasm.github.io/wasm-pack/installer/init.sh
-> 200

Saved evidence includes both responses with headers and bodies, plus the rendered deployed page's link list. The source at fa985df contains the same URL.

Limitations: no repository build, installer script execution or platform-install test was performed. The docs link-checker configuration (.linkinatorrc.json at fa985df) does not skip this host, but no current CI diagnostic artifact was consumed; the evidence here is the direct public GET.

Existing work checked

Searched open and closed issues and PRs in hyperledger-identus/docs (full title inventory of 62 issues and 238 PRs) and in hyperledger-identus/sdk-ts for wasm-pack, rustwasm, installer and prerequisites, and read matching bodies and diffs.

  • sdk-ts issue #475 (closed) reported this same deprecated upstream installer URL in the SDK README, and sdk-ts PR #476 (merged 2026-01-13) updated that README only. It did not cover this portal page, so this is an independently owned, still-live instance rather than a reopened or replacement record of #475.
  • No open or closed docs issue/PR matches this link, and no open repair was found.

Acceptance criteria

  • The wasm-pack prerequisite link in the Quick Start resolves to maintained installation guidance.
  • A verification GET for the linked URL returns 200.
Lingua principale
TypeScript
Stelle
15
Fork
8
Merge medio
3g 14h
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di hyperledger-identus/docs

Tutte le issue di hyperledger-identus/docs

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.