crates.io · #2566 most downloaded on crates.io

ws_stream_wasm

0.7.516M downloads/monajamelan/ws_stream_wasm ↗New releases in your daily digest, changelog included.

A convenience library for using websockets in WASM

Last release 1 years ago
08 Jun 2025
Ships unpredictably
gaps range from 2 weeks to 2.4 years
Most releases are documented
notes for 15 of 18 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
19 releases · first in 2019

Release timeline

19 releases since 2019

20192020202120222023202420252026

Releases

0.7.58 Jun 2025
dev: update edition to 2024 Bump version Add Cargo.lock to git Add note about direct sockets protocol fix send binary with target_feature = atomics Do
dev:
update edition to 2024
Bump version
Add Cargo.lock to git
Add note about direct sockets protocol
fix send binary with target_feature = atomics
Dont try to test WSS in CI as its a PITA
fix clippy errors
Add rustflags for getrandom
silence false positive clippy warning
bring back getrandom feature for wasm
update cargo-deny
update dependencies
Typos
Test connecting to wss
Fix warning for nightly cfg
Report error rather than panicking with unreachable!
Open source →
Additional notes2 sources agree
Fixed

Don't panick when receiving an unknown error from the browser (thanks @gibbz00)

Test connecting to WSS, unfortunately does not work in CI because we'd need to add the mkcert CA to the firefox and chrome profiles that wasm-pack creates.

update dependencies

allow compilation with target_feature = atomics by copying the data into the websocket (thanks @robtfm)
Open source →

dev:
Changelog and version number.
Update github actions.
Clippy warnings.
On future drop while connecting, close ws and log warning.
Fix a bug where the onerror callback could try to be called when it had already been destroyed.
Use cargo deny github action.
Update send_wrapper.
Add liberapay tag.
Update tokio-util.

Open source →

Additional notes2 sources agree

Fixed

When the WsMeta::connect future is dropped, close websocket and unregister callbacks. This avoids some ugly error messages in the console. Thanks to @hamchapman for discovering and solving the issue and @danielhenrymantilla for reviewing the solution.

Updated

tokio-util to 0.7 (dev-dependency)
send_wrapper to 0.6

Open source →

0.7.328 Jun 2021

dev: update todo Make WsStream Sync .

dev:
update todo
Make WsStream Sync.

Open source →

Additional notes2 sources agree

Added

on user demand also make WsStream Sync again.

Open source →

0.7.226 Jun 2021

dev: Rename master branch to release Bump version and changelog. Add a test for Send-ness of WsStream and WsMeta. Fix some documentation warnings. Mak

dev:
Rename master branch to release
Bump version and changelog.
Add a test for Send-ness of WsStream and WsMeta.
Fix some documentation warnings.
Make sure WsStream is Send.

Open source →

Additional notes2 sources agree

Added

Make WsStream Send again.

Open source →

0.7.111 Jun 2021

dev: Bump version and changelog. fix clippy warnings. Switch to asynchronous_codec. Fix external_doc for rustdoc 1.54. Clean up one test. Fix build st

dev:
Bump version and changelog.
fix clippy warnings.
Switch to asynchronous_codec.
Fix external_doc for rustdoc 1.54.
Clean up one test.
Fix build status badge in readme.

Open source →

Additional notes2 sources agree

Updated

Switch to asynchronous-codec.
Remove external_doc feature for nightly 1.54.

Open source →

0.7.018 Feb 2021

dev: Migrate to github CI. Update pharos to 0.5 Browser change, no longer throw for forbidden port. improve contribution guidelines. Fix small error i

dev:
Migrate to github CI.
Update pharos to 0.5
Browser change, no longer throw for forbidden port.
improve contribution guidelines.
Fix small error in the README.md. (#3)

Open source →

Additional notes2 sources agree

BREAKING CHANGE: Update to tokio v1, pharos to 0.5 and async_io_stream to 0.3.
- BREAKING CHANGE: Browsers stopped raising SECURITY_ERR when trying to connect to a forbidden port. It now just returns a connection failed, which is indistinguishable from any other network problems, or simply the server not listening on this port. This is an intended change.

Open source →

0.7.0-beta.13 Nov 2020pre-release

dev: Even without cache it seems to be there. Remove wasm-pack from the cache in CI. Don't publish code with local path deps... Actually run cargo den

dev:
Even without cache it seems to be there.
Remove wasm-pack from the cache in CI.
Don't publish code with local path deps...
Actually run cargo deny in CI.
Fix clippy warnings.
Version bump and changelog.
Work around futures-codec not using latest Bytes version.
Update cargo-deny,
Update dependencies (tokio 0.3)

Open source →

Additional notes2 sources agree

Update to tokio 0.3, will be out of beta when tokio hits 1.0.

Open source →

0.6.12 Oct 2020

dev: Prep release 0.6.1 remove unneeded muts. add deny.toml and improve travis configuration. add more instructions to Cargo.yml Improve readme

dev:
Prep release 0.6.1
remove unneeded muts.
add deny.toml and improve travis configuration.
add more instructions to Cargo.yml
Improve readme

Open source →

Additional notes2 sources agree

Remove unnecessary mut in recent compiler versions. Travis stable on osx is still on 1.44 and will fail until they upgrade.
- improve readme

Open source →

0.6.021 Mar 2020

dev: (41 commits) fix: to many categories. chore: update changelog. chore: remove debug and trace logs. chore: fix clippy warnings. give up on windows

dev: (41 commits)
fix: to many categories.
chore: update changelog.
chore: remove debug and trace logs.
chore: fix clippy warnings.
give up on windows CI again
try windows tests on CI.
General cleanup
Return error when string messages fail to decode.
don't build dependencies on CI when cargo doc
turn missing docs into warning instead of hard error.
docs.rs only build on default target.
finish documentation.
add readme for examples
try to fix CI.
fix doc configuration
get async_io_stream from crates, should fix CI.
Clean up CI
Documentation: use -cfg instead of a feature to enable docs features.
Move the closures to WsStream as we allow dropping WsMeta early and WsStream relies on the closures to function.
Do not set a close code if the user doesn't
...

Open source →

Additional notes2 sources agree

BREAKING CHANGE: rename the basic types. WsStream is now called WsMeta and WsIo is now called WsStream.
- BREAKING CHANGE: WsStream no longer implements AsyncRead/AsyncWrite directly, you have to call into_io().
- BREAKING CHANGE: The error type is now renamed to WsErr and is an enum directly instead of having an error kind.
- BREAKING CHANGE: Fix: From<MessageEvent> for WsMessage has become TryFrom. This is because things actually could go wrong here.
- Implement tokio AsyncRead/AsyncWrite for WsStream (Behind a feature flag).
- delegate implementation of AsyncRead/AsyncWrite/AsyncBufRead to async_io_stream. This allows sharing the functionality with ws_stream_tungstenite, fleshing it out to always fill and use entire buffers, polling the underlying stream several times if needed.
- only build for default target on docs.rs.
- exclude unneeded files from package build.
- remove trace and debug statements.
- WsMessage now implements From<Vec<u8>> and From<String>.
- WsMeta and WsStream are now Send. You should still only use them in a single thread though. This is fine because WASM has no threads, and is sometimes necessary because all the underlying types of web-sys are !Send.
- No longer set a close code if the user doesn't set one.
- Fix: Make sure WsStream continues to function correctly if you drop WsMeta.

Open source →

0.4.023 Sept 2019Breaking2 sources agree

BREAKING CHANGE: use the new filter feature from pharos, making NextEvent and WsEventType redundant. Those types have been removed from the library. T…

BREAKING CHANGE: use the new filter feature from pharos, making NextEvent and WsEventType redundant. Those types have been removed from the library. The observe and method off WsStream now takes a pharos::ObserveConfig to filter event types. Please refer to the documentation of pharos for how to use them.
- spell check all docs

Open source →

0.2.02 Aug 2019Breaking2 sources agree

BREAKING CHANGE: Fix: Correctly wake up tasks waiting for a next message if the connection gets closed externally. This prevents these tasks from hang…

BREAKING CHANGE: Fix: Correctly wake up tasks waiting for a next message if the connection gets closed externally. This prevents these tasks from hanging indefinitely. As a consequence, WsStream::close now returns a Result, taking into account that if the connection is already closed, we don't have the CloseEvent. Instead a WsErr of kind WsErrKind::ConnectionNotOpen is returned.
- update to async_runtime 0.3

Open source →