Skip to content

Officially support wasm32-unknown-unknown #218

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.

Sign up for GitHub

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

Jump to bottom
Closed
LegNeato opened this issue Aug 10, 2018 · 4 comments
Closed

Officially support wasm32-unknown-unknown #218

LegNeato opened this issue Aug 10, 2018 · 4 comments
Labels
enhancement Improvement of existing features or bugfix p::minor Minor priority for implemetation

Comments

@LegNeato
Copy link
Member

We appear to work with wasm32-unknown-unknown. It would be nice to build with it in CI, as well as have an example where it is used in node. I'd be curious as to the perf, as rust/wasm is generally faster than js but most js graphql server implementations are async.
@LegNeato LegNeato added enhancement Improvement of existing features or bugfix p::minor Minor priority for implemetation labels Aug 10, 2018
@theduke
Copy link
Member

theduke commented Sep 13, 2018

The really interesting use case here for me would be offline support.

As in, writing your GraphQL backend only once, with some for of compatability layer for database access.
Compiling the backend down to wasm and then using it in the browser in offline mode would be a pretty rad feature.

@LegNeato
Copy link
Member Author

Oh yeah, that would be cool. If the DB was https://realm.io/products/realm-database/ your changes would get transparently synced when you went back online too.

willglynn added a commit to willglynn/juniper that referenced this issue Nov 16, 2018
@willglynn
Build wasm32-unknown-unknown in CI (graphql-rust#218)
c1dbe61 
`cargo check --wasm32-unknown-unknown` is sufficient to demonstrate that the
`juniper` and `juniper_codegen` crates can compile for WebAssembly, which should
help avoid accidental regressions.
willglynn added a commit to willglynn/juniper that referenced this issue Nov 16, 2018
@willglynn
Build wasm32-unknown-unknown in CI (graphql-rust#218)
d605059 
`cargo check --wasm32-unknown-unknown` is sufficient to demonstrate that the
`juniper` and `juniper_codegen` crates can compile for WebAssembly, which should
help avoid accidental regressions.
@willglynn willglynn mentioned this issue Nov 16, 2018
Merged
willglynn added a commit to willglynn/juniper that referenced this issue Nov 16, 2018
@willglynn
Build wasm32-unknown-unknown in CI (graphql-rust#218)
94eafff 
`cargo check --wasm32-unknown-unknown` is sufficient to demonstrate that the
`juniper` and `juniper_codegen` crates can compile for WebAssembly, which should
help avoid accidental regressions.
LegNeato pushed a commit that referenced this issue Dec 7, 2018
@willglynn @LegNeato
Build wasm32-unknown-unknown in CI (#278)
4858f90 
* Build wasm32-unknown-unknown in CI (#218)

`cargo check --wasm32-unknown-unknown` is sufficient to demonstrate that the
`juniper` and `juniper_codegen` crates can compile for WebAssembly, which should
help avoid accidental regressions.
@theduke
Copy link
Member

theduke commented Dec 19, 2018

@LegNeato guess this can be closed?

@LegNeato
Copy link
Member Author

Yeah, I think we are ok for now. I still want to have a node example but that can come later.

@dustin-rcg dustin-rcg mentioned this issue Oct 30, 2022
Closed
@ma2bd ma2bd mentioned this issue Nov 11, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Improvement of existing features or bugfix p::minor Minor priority for implemetation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@theduke @LegNeato