Skip to content

Making BroadcastChannel global #38803

Closed
Closed
Making BroadcastChannel global#38803
Labels
feature requestIssues requesting new Node.js features.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

Description

@hsablonniere
hsablonniere
opened on May 24, 2021

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...

Activity

  1. Ayase-252
    added
    feature requestIssues requesting new Node.js features.
    on May 25, 2021

  2. aduh95 commented on May 25, 2021

    @aduh95
    aduh95
    on May 25, 2021
    Contributor

    BroadcastChannel is still documented as experimental, we probably want to wait to have a stable implementation fully compatible with the one exposed by browsers before making it global.
    Pinging @jasnell as he is the one who did the initial implementation.

  3. bnoordhuis
    added a commit that references this issue on Feb 15, 2022

    test: run webmessaging/broadcastchannel WPT

    9153384
  4. nodejs-github-bot
    added a commit that references this issue on Feb 17, 2022

    test: run webmessaging/broadcastchannel WPT

    9caceb2
  5. bengl
    added 5 commits that reference this issue on Feb 21, 2022

    test: run webmessaging/broadcastchannel WPT

    602acb2

    test: run webmessaging/broadcastchannel WPT

    5d5be6e

    test: run webmessaging/broadcastchannel WPT

    b3e863e

    test: run webmessaging/broadcastchannel WPT

    c59dd98

    test: run webmessaging/broadcastchannel WPT

    9825ced

  6. github-actions commented on Mar 24, 2022

    @github-actions
    github-actionsbot
    on Mar 24, 2022
    Contributor

    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.

  7. github-actions
    added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Mar 24, 2022

  8. aduh95 commented on Mar 24, 2022

    @aduh95
    aduh95
    on Mar 24, 2022
    Contributor

    Fixed by ce4d3ad.

  9. aduh95
    closed this as completedon Mar 24, 2022
  10. targos
    added this to Node.js feature requestson Mar 24, 2022
  11. targos
    moved this from Pending Triage to Done in Node.js feature requestson Mar 24, 2022
  12. targos
    moved this to Pending Triage in Node.js feature requestson Mar 24, 2022
  13. danielleadams
    added 2 commits that reference this issue on Apr 21, 2022

    test: run webmessaging/broadcastchannel WPT

    55f7a6d

    test: run webmessaging/broadcastchannel WPT

    3e354da
  14. avivkeller
    removed this from Node.js feature requestson Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestIssues requesting new Node.js features.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions