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

chore: Remove stdweb feature from instant crate to circumvent downstream issues with stdweb/wasm-bindgen #86

Merged
merged 2 commits into from May 22, 2023

Conversation

jsantell
Copy link
Contributor

@jsantell jsantell requested review from cdata and a team as code owners May 19, 2023 20:41
@bgins
Copy link
Contributor

bgins commented May 19, 2023

Hey @jsantell 👋

I'm working on adding JS packaging support on a local branch, and I also ran into this issue. I was able to resolve it by dropping the stdweb feature from the instant dependency:

instant = { version = "0.1", features = ["wasm-bindgen", "stdweb"] }

According to the instant docs, it is only necessary to use either the wasm-bindgen or stdweb feature: https://github.com/sebcrozet/instant#instant. What would you think about dropping stdweb instead of pinning wasm-bindgen? It seems that stdweb is unmaintained, so there might never be a fix for it.

@cdata
Copy link
Member

cdata commented May 19, 2023

Yeah 👍 to @bgins let's try dropping stdweb!

@jsantell jsantell changed the title chore: Pin wasm-bindgen versions to circumvent issues with wasm-bindgen > 0.2.84 chore: Remove stdweb feature from instant crate to circumvent downstream issues with stdweb/wasm-bindgen May 19, 2023
@jsantell
Copy link
Contributor Author

Hey @jsantell wave

I'm working on adding JS packaging support on a local branch, and I also ran into this issue. I was able to resolve it by dropping the stdweb feature from the instant dependency:

instant = { version = "0.1", features = ["wasm-bindgen", "stdweb"] }

According to the instant docs, it is only necessary to use either the wasm-bindgen or stdweb feature: https://github.com/sebcrozet/instant#instant. What would you think about dropping stdweb instead of pinning wasm-bindgen? It seems that stdweb is unmaintained, so there might never be a fix for it.

SGTM! Updated PR with your suggestion

Copy link
Contributor

@bgins bgins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! 🎉

@codecov-commenter
Copy link

Codecov Report

Merging #86 (3ed84bd) into main (f75b00a) will increase coverage by 0.05%.
The diff coverage is n/a.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main      #86      +/-   ##
==========================================
+ Coverage   57.47%   57.52%   +0.05%     
==========================================
  Files          23       23              
  Lines         776      777       +1     
  Branches      187      187              
==========================================
+ Hits          446      447       +1     
  Misses        202      202              
  Partials      128      128              

see 1 file with indirect coverage changes

@cdata
Copy link
Member

cdata commented May 22, 2023

Looks like one lint to fix for nightly's sake @jsantell others looks great

@jsantell
Copy link
Contributor Author

Updated fixing the nightly lint on RawCodec::default()

Copy link
Member

@cdata cdata left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Woot!

@cdata cdata merged commit 67ec64d into ucan-wg:main May 22, 2023
5 checks passed
@github-actions github-actions bot mentioned this pull request May 22, 2023
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 this pull request may close these issues.

None yet

4 participants