Update dependency terser to v5.37.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
terser (source)	5.36.0 -> 5.37.0

---

Release Notes

terser/terser (terser)

v5.37.0

Compare Source

• Reserved object properties from chrome extensions (domprops)
• Fix semicolon insertion between a class property without a semicolon a and a computed class property ["prop"]

v5.36.0

Compare Source

• Support import attributes with syntax

v5.35.0

Compare Source

• Ensure parent directory exists when using --output on CLI (#​1530)

v5.34.1

Compare Source

• bump the rollup devDependency to disable CVE warnings (Terser was not affected)

v5.34.0

Compare Source

• internal: stop assigning properties to objects they don't belong in
• internal: run compress tests in parallel
• drop_console: emit an empty function if the return value of console.METHOD(...) may be called.

v5.33.0

Compare Source

• reduce_vars improved when dealing with hoisted function definitions (#​1544)

v5.32.0

Compare Source

• import("module") can now be input and output from ESTree AST (#​1557)
• BigInt literals can now be input and output from ESTree AST (#​1555)
• typeof an object or array (typeof {} and typeof []) can now be statically evaluated. (#​1546)

v5.31.6

Compare Source

• Retain side effects in a case when the expression is a sequence (comma) expression

v5.31.5

Compare Source

• Revert v5.31.4, which created mysterious issues #​1548, #​1549

v5.31.4

Compare Source

• drop_unused: drop classes which only have side effects in the extends part

v5.31.3

Compare Source

• drop_unused: drop unused parameters from IIFEs in some more situations.

v5.31.2

Compare Source

• drop_unused: scan variables in self-referential class declarations that contain side effects.
• Don't add parens to arrow function when it's the default for an argument (#​1540)
• Update domprops (#​1538)

v5.31.1

Compare Source

• Allow drop-unused to drop the whole assignment (not just the assigned name) in more situations, in order to avoid duplication of long strings.

v5.31.0

Compare Source

• Sync up property mangler exceptions with current contents of Firefox and Chrome environments
• Add more webcomponent properties to property mangler exceptions (#​1525)
• Drop non-nullish constants in ...spreads in objects (#​1141)

v5.30.4

Compare Source

• Fix parsing #private in ... when next to other operators

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

Summary by Sourcery

Build:

• Update terser dependency from version 5.36.0 to 5.37.0 in package.json.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 21 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
bench/vercel                             |  WARN  deprecated [email protected]
/tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/next-swc/crates/next-dev-tests/tests:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@turbo%2Fpack-test-harness: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/next-swc/crates/next-dev-tests/tests

@turbo/pack-test-harness is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.
.                                        |  WARN  deprecated @babel/[email protected]

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 24db280

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates the terser dependency from version 5.36.0 to 5.37.0 in the Next.js package. The update includes improvements to object property handling for Chrome extensions and fixes a semicolon insertion issue between class properties.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Dependency version update for the terser package	Updated terser from 5.36.0 to 5.37.0 Added support for reserved object properties from Chrome extensions Fixed semicolon insertion between class properties	packages/next/package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.