Skip to content
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.

Support for WASM: Add CI for wasm32-unknown-unknown #37

Closed
Mythra opened this issue Jul 16, 2020 · 2 comments · Fixed by #38
Closed

Support for WASM: Add CI for wasm32-unknown-unknown #37

Mythra opened this issue Jul 16, 2020 · 2 comments · Fixed by #38

Comments

@Mythra
Copy link
Contributor

Mythra commented Jul 16, 2020

👋 ,

We have a particular use case that involves deploying to a WASM target, and although the crate seems to build fine with WASM, and work it'd be nice to have continuous integration running on this project that confirms all is working okay as time goes on. FWIW tracing is currently in the same boat: tokio-rs/tracing#642
@Mythra
Copy link
Contributor Author

Mythra commented Jul 16, 2020

Also we'd be happy to work on the wasm side of things if you'd like, do any testing/validation. I just really wanna get a feeling check making sure this is okay to do. 😄

@yaahc
Copy link
Collaborator

yaahc commented Jul 16, 2020

I am 100% on board with adding wasm to CI, especially if you're already happy to contribute the changes needed.

@Mythra Mythra mentioned this issue Jul 16, 2020
Merged
@yaahc yaahc closed this as completed in #38 Jul 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add testing for wasm
2 participants
@yaahc @Mythra