-
Notifications
You must be signed in to change notification settings - Fork 36
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
Use js_sys
to enable node.js compatibility
#18
base: master
Are you sure you want to change the base?
Conversation
Co-authored-by: Thoralf-M <[email protected]>
We had an issue with In the browser this is not really noticeable, but it prevents I marked the PR as ready for review, @tomaka or @mxinden - if you have time, we would appreciate it! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-authored-by: Max Inden <[email protected]>
Again, thanks for the work you are putting into this @PhilippGackstatter. Before we continue here, I would be curious what your input on libp2p/rust-libp2p#2143 (comment) would be. |
Crossreferencing related pull request here libp2p/rust-libp2p#2245 |
@mxinden the linked approach only works for browser, but not for node.js, so we can't use the same :( |
@mxinden can we go forward with this PR or what's holding it up? |
@Thoralf-M libp2p/rust-libp2p#2245 removed |
We use it in our crate independent of libp2p |
I am sorry, but I am afraid I won't be able to help you here. I am not maintaining this library, nor do I have the capacity to do so in the future. You might want to consider switching to |
This is motivated by us wanting to use
libp2p
in our Wasm bindings for web and node.js. This also follows from discussion in issue 2143 in rust-libp2p. The main idea for this comes from the instant crate.I have tested the changes manually within our project and no problems came up. Is this something I should add automatic tests for? And if so, any hints on how to do that?
Thanks!