We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm not sure if this is the right place to report, but the demo on Glitch linked to from https://developer.chrome.com/docs/capabilities/web-apis/websocketstream does
const { ... } = await wss.connection;
while the correct API seems to be
const { ... } = await wss.opened;
The text was updated successfully, but these errors were encountered:
Thanks! I will update it.
Sorry, something went wrong.
Duh, past me thought of updating the article, but forgot to reflect the change in the demo. It's fixed now. Thanks for the heads-up!
No problem :) It looks good now, thanks. I'll let you close the issue.
No branches or pull requests
I'm not sure if this is the right place to report, but the demo on Glitch linked to from https://developer.chrome.com/docs/capabilities/web-apis/websocketstream does
const { ... } = await wss.connection;
while the correct API seems to be
const { ... } = await wss.opened;
The text was updated successfully, but these errors were encountered: