Description

While reading wasm-pack and wasm-bindgen recently, I remembered this excluded test case. Cyclic import handling might not exactly follow the future spec in https://github.com/WebAssembly/esm-integration but I think this feature looks usable after minor fix.

todo

• test latest non-cyclic version of wasm-bindgen example

references

• esm: --experimental-wasm-modules integration support nodejs/node#27659
• Support Wasm files that import JS resources jestjs/jest#13608
• Get rid of the circular dependency when targeting ES modules wasm-bindgen/wasm-bindgen#3152
  • wasm-bindgen recently removed cyclic import between wasm and js, but the example currently uses old the old pattern, which turns out to be a nice case to exercise cyclic import scenario, so I'm keeping this test case.
• fix: declare ES module in package.json wasm-bindgen/wasm-pack#1061
• https://github.com/WebAssembly/esm-integration/tree/main/proposals/esm-integration
• https://github.com/WebAssembly/esm-integration/blob/main/proposals/esm-integration/EXAMPLES.md#js---wasm-cycle-where-js-is-higher-in-the-module-graph

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.