Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to disable wasmbind feature to prevent wasm interface polution #191

Open
8e8b2c opened this issue Aug 16, 2024 · 0 comments
Open

Comments

@8e8b2c
Copy link
Contributor

8e8b2c commented Aug 16, 2024

I'm using typeshare with a project that builds a wasm module that must conform to a specific interface. Once I add the typeshare crate to my dependencies for the purpose of annotating my types, my wasm module's exports become tainted:

Compile(\"Error while importing \\\"__wbindgen_placeholder__\\\".\\\"__wbindgen_describe\\\": unknown import. Expected Function(FunctionType { params: [I32], results: [] })\") }), wasm_trace: [] }))"))

The culprit appears to be the wasmbind feature on chrono.

I have a fix/workaround that's easy enough: make wasmbind an optional but default feature. I'll open a PR shortly.

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

No branches or pull requests

1 participant