You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since unwasm is aware of wasm imports, it can also try to search for them from parent package.json's imports field (docs) to be zero-config for .wasm imports that require a binding.
(Funny, I was thinking about supporting .imports.js file alongside .wasm files as a convention until I suddenly thought, oh hey ESM already got it converted!)
I think this should give us a clear path for package authors' convention (#7)
The text was updated successfully, but these errors were encountered:
Since unwasm is aware of wasm imports, it can also try to search for them from parent
package.json
'simports
field (docs) to be zero-config for.wasm
imports that require a binding.(Funny, I was thinking about supporting
.imports.js
file alongside.wasm
files as a convention until I suddenly thought, oh hey ESM already got it converted!)I think this should give us a clear path for package authors' convention (#7)
The text was updated successfully, but these errors were encountered: