Repository navigation
0.4.1
Fixes for the checks of the community catalog. Nothing changes in how Tropa works.
Changed
- The release holds only
main.js,manifest.jsonandstyles.css, with GitHub artifact attestations for them (gh attestation verify main.js -R Darkildo/tropa). The demo vaults moved to a release of their own,demo, updated with every version; the links in the README point there. - The layout engine's WebAssembly is kept in git (
assets/wasm/tropa_layout.wasm), sonpm ci && npm run buildworks without Rust and gives the samemain.jsas the release. CI still builds it twice fromcrates/tropa-layoutand fails unless both builds match the file in git byte for byte. - The console stays quiet unless something fails: which layout engine runs, and why WebAssembly was skipped, are kept in the layout statistics instead of the console, and the notices of the bundled ts-fsrs are left out of
main.js. - The learning journal is read by walking its own folder instead of every Markdown file of the vault.
- The phone progress bar hides its text without
clip-path, which the catalog check marks as only partly supported. - The README has a Privacy section: what Tropa reads and writes, and that it makes no network requests.
Layout engine WebAssembly (inlined in main.js), sha256 a88682595bad6ac1378b5cd6017b37b0d1d93591b11d2f50eb48a1126214d4cc. Rebuild it from the source of this tag with npm run build:wasm.