Skip to content

Stop using Symbol.dispose #267

Closed

Description

@rijenkii

Using Symbol.dispose right now is a bad idea. It is only supported starting with chrome 134, and Explicit Resource Management proposal is only at stage 3 of 4.

Fix released in 3.0.1 does not work, judging by comments on #260 and my own experience.

Activity

  1. rijenkii commented on Mar 3, 2025

    @rijenkii
    ContributorAuthor

    Fix submitted, waiting for review.

  2. nuintun commented on Mar 5, 2025

    @nuintun

    Symbol.dispose is available and correctly transpiled by TypeScript, but it's polyfill being removed during bundler tree-shaking due to misconfigured sideEffects settings.

    See: #270

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions