Skip to content

Terser options types are outdated #17668

Closed

Description

@luc122c

Describe the bug

The type definitions for Terser (defined here) are outdated and do not match the source. I'll gladly open a PR to update them, however I notice the line that says "Modified and inlined to avoid extra dependency". I'm not sure what the modifications would be and don't want to overwrite them.

Reproduction

N/A

Steps to reproduce

No response

System Info

System:
    OS: macOS 14.5
    CPU: (20) arm64 Apple M1 Ultra
    Memory: 17.08 GB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node
    Yarn: 3.6.3 - ~/.nvm/versions/node/v20.11.0/bin/yarn
    npm: 10.2.4 - ~/.nvm/versions/node/v20.11.0/bin/npm
    pnpm: 9.4.0 - ~/.nvm/versions/node/v20.11.0/bin/pnpm
    bun: 1.1.18 - /opt/homebrew/bin/bun
  Browsers:
    Chrome: 126.0.6478.127
    Safari: 17.5

Used Package Manager

pnpm

Logs

No response

Validations

Activity

  1. changed the title [-]Terser options are outdated[/-] [+]Terser options types are outdated[/+] on Jul 12, 2024
  2. added a commit that references this issue on Jul 15, 2024
    b723a75
  3. locked and limited conversation to collaborators on Jul 30, 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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions