Skip to content

Conversation

@elliotwutingfeng
Copy link
Contributor

@elliotwutingfeng elliotwutingfeng commented Sep 30, 2025

  • Prevents PlatformWeb from loading entropy source from null on Node.
  • Node.js / Browser detection no longer relies on try/catch; replaced with null check for JavaScript process.versions.node. If it is not null, it is Node, otherwise it is probably a web browser.
  • Increase timeout to 2x for Chrome tests as the default timeout is insufficient.
  • Implementation no longer depends on js_interop_unsafe

Closes #257

@elliotwutingfeng elliotwutingfeng changed the title fix: catch UnknownJSTypeError for node and chrome platform. Catch UnknownJSTypeError for Node and increase timeout for Chrome workflow. Oct 2, 2025
@elliotwutingfeng elliotwutingfeng changed the title Catch UnknownJSTypeError for Node and increase timeout for Chrome workflow. Use process.versions.node to check for Node.js environment and increase timeout for Chrome workflow. Dec 19, 2025
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.

Is it safe to use 4.0.0 given CI failures for Chrome and Node?

2 participants