Skip to content

Remove WASI dependencies from WASM interpreter#1274

Open
DamianReeves wants to merge 1 commit intovnextfrom
fix/wasm-no-wasi-http
Open

Remove WASI dependencies from WASM interpreter#1274
DamianReeves wants to merge 1 commit intovnextfrom
fix/wasm-no-wasi-http

Conversation

@DamianReeves
Copy link
Copy Markdown
Member

Summary

  • Add --disable all to jco componentize to produce a pure computation component
  • Removes all WASI imports (wasi:http, wasi:io, wasi:clocks, wasi:random) that were added by ComponentizeJS defaults
  • The interpreter only exports morphir:interpreter/types and morphir:interpreter/eval — no imports needed

Before

world root {
  import wasi:http/...
  import wasi:io/...
  import wasi:clocks/...
  import wasi:random/...
  export morphir:interpreter/types;
  export morphir:interpreter/eval;
}

After

world root {
  export morphir:interpreter/types;
  export morphir:interpreter/eval;
}

Test plan

  • mise run build:interpreter-wasm builds successfully
  • mise run test:interpreter-wasm — 11 tests pass, 38 assertions
  • npx jco wit confirms zero imports

Add --disable all to jco componentize to produce a pure computation
component with no WASI imports (no wasi:http, wasi:io, wasi:clocks,
wasi:random). The interpreter only needs its own morphir:interpreter
exports — it has no I/O requirements.
@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant