-
Notifications
You must be signed in to change notification settings - Fork 16
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
[Request] Support wasm with chrono #16
Comments
Thanks for the suggestion! I'll take a look at this as soon as I get a chance. In the meantime, I'd have no issue accepting an MR |
As far as I can tell Please check e2d994a or later and see if it works for you |
Hi @mplanchard. It doesn't work for me. However, prisma has a wasm-compatible fix at prisma/prisma#17102 (comment) |
@erenaspire7 doesn't work in what way? The wasm build works fine in CI for those targets. |
@mplanchard . So my use-case was inter-oping the package with typescript using wasm. It failed due to not having an equivalent for SystemTime within rust from the standard library Prisma addressed this by using a web_time dependency |
Oh, is it this runtime issue? rust-lang/rust#48564 Didn't realize the stdlib had stuff that would compile for a target but unequivocally panic at runtime |
Yeah, that's the issue. Thanks! |
Great. I've got a wasm test now that shows the issue. I'll update to a different time dependency and get that pushed. Thanks for the lead! |
Hey @mplanchard, hopefully I can push a PR within the next 7 days. |
Thanks! I may have it done by then, depends on work stuff. The master branch should work now, just working on getting the github actions tests cleaned up |
Same in title, The team can support wasm?
time::SystemTime not support in wasm, but chrono support it
The text was updated successfully, but these errors were encountered: