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

Add support for target wasm32-unknown-unknown #84

Open
dougEfresh opened this issue Dec 3, 2024 · 2 comments · May be fixed by #85
Open

Add support for target wasm32-unknown-unknown #84

dougEfresh opened this issue Dec 3, 2024 · 2 comments · May be fixed by #85

Comments

@dougEfresh
Copy link

I like to add support for wasm32-unknown-uknown target (aka browser support)

Someone already created a client

Without changing much code and using #[cfig.(..)] macro will allow compiling to wasm target.

@dougEfresh dougEfresh linked a pull request Dec 3, 2024 that will close this issue
2 tasks
@chris13524
Copy link
Member

What is your use case for WASM support in this repo? The other WalletConnect client you linked doesn't depend on this repo, and we are not planning to create an official WalletConnect Rust client soon.

@dougEfresh
Copy link
Author

The repo/crate I reference copied a bunch of code from this repo, e.g. ProjectId
No need to release any official rust client or publish a javascript package.

With respect to use case, rust wasm is gaining momentum. There are several competing and great web frameworks.

The PR is the foundation I need to build webapps/browser extensions that only support reown protocol.

Side note and personal opinion, the rust ecosystem for web developer is more robust and hassle free when compared to javascript/typescript.

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

Successfully merging a pull request may close this issue.

2 participants