-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Making BroadcastChannel global #38803
Comments
|
Refs: nodejs#38803 PR-URL: nodejs#41962 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Mestery <mestery@protonmail.com>
Refs: nodejs#38803 PR-URL: nodejs#41962 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Mestery <mestery@protonmail.com>
There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment. For more information on how the project manages feature requests, please consult the feature request management document. |
Fixed by ce4d3ad. |
Refs: nodejs#38803 PR-URL: nodejs#41962 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Mestery <mestery@protonmail.com>
Hi wonderful Node.js team!
I was wondering if making
BroadcastChannel
available as a global variable was considered.I'm working on a project where I created a class that composes a BroadcastChannel, some kind of layer on top of it. I need this on both client AND server side. Right now, I need a Node.js version with
import { BroadcastChannel } from 'worker_threads'
and a browser version that can rely on global.Thanks...
The text was updated successfully, but these errors were encountered: