Skip to content

v0.3.1 — npm tarball fixes (examples + perry-ffi docs)

Choose a tag to compare

@proggeramlug proggeramlug released this 19 May 10:38

Patch release fixing two issues reported against the v0.3.0 tarball.

Fixed

  • examples/ now shipped. native/{macos,ios,windows,linux}/Cargo.toml declare [[example]] blocks (demo_editor, etc.) but examples/ wasn't in the npm files: list. cargo build failed with can't find demo_editor example at examples/demo_editor.rs. Tarball grew from 121 → 140 files.

  • perry-ffi resolution documented. native/{macos,ios}/Cargo.toml use perry-ffi = { path = \"../../../../perry/perry/crates/perry-ffi\" } — a sibling-checkout path that doesn't survive npm install. The real fix needs Perry to publish perry-ffi to crates.io (filed PerryTS/perry#1112). Until then:

    • New native/NATIVE_CRATES.md — consumer setup guide with the [patch.crates-io] workaround.
    • README has a "Consuming the native crates from npm" section linking to it.
    • Comment block above the perry-ffi line in each affected Cargo.toml points at both.

Web target unaffected

native/web/dom-ffi.ts + native/web/tree-sitter-bridge.ts are pure TypeScript — no Rust build path, no perry-ffi. The import { mount } from '@honeide/editor/web' flow added in v0.3.0 just works.

Found by

@honeide/editor consumers using the macOS native crate from a Perry app after npm install.