build(deps-dev): bump esbuild from 0.19.5 to 0.19.8

[dependabot]

Bumps esbuild from 0.19.5 to 0.19.8.

Release notes

Sourced from esbuild's releases.

v0.19.8

• Add a treemap chart to esbuild's bundle analyzer (#2848)

  The bundler analyzer on esbuild's website (https://esbuild.github.io/analyze/) now has a treemap chart type in addition to the two existing chart types (sunburst and flame). This should be more familiar for people coming from other similar tools, as well as make better use of large screens.

• Allow decorators after the export keyword (#104)

  Previously esbuild's decorator parser followed the original behavior of TypeScript's experimental decorators feature, which only allowed decorators to come before the export keyword. However, the upcoming JavaScript decorators feature also allows decorators to come after the export keyword. And with TypeScript 5.0, TypeScript now also allows experimental decorators to come after the export keyword too. So esbuild now allows this as well:

  // This old syntax has always been permitted:
  @decorator export class Foo {}
  @decorator export default class Foo {}
  // This new syntax is now permitted too:
  export @​decorator class Foo {}
  export default @​decorator class Foo {}

  In addition, esbuild's decorator parser has been rewritten to fix several subtle and likely unimportant edge cases with esbuild's parsing of exports and decorators in TypeScript (e.g. TypeScript apparently does automatic semicolon insertion after interface and export interface but not after export default interface).

• Pretty-print decorators using the same whitespace as the original

  When printing code containing decorators, esbuild will now try to respect whether the original code contained newlines after the decorator or not. This can make generated code containing many decorators much more compact to read:

  // Original code
  class Foo {
    @a @b @c abc
    @x @y @z xyz
  }
  // Old output
  class Foo {
  @​a
  @​b
  @​c
  abc;
  @​x
  @​y
  @​z
  xyz;
  }
  // New output
  class Foo {
  @​a @​b @​c abc;
  @​x @​y @​z xyz;
  }

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.19.8

• Add a treemap chart to esbuild's bundle analyzer (#2848)

  The bundler analyzer on esbuild's website (https://esbuild.github.io/analyze/) now has a treemap chart type in addition to the two existing chart types (sunburst and flame). This should be more familiar for people coming from other similar tools, as well as make better use of large screens.

• Allow decorators after the export keyword (#104)

  Previously esbuild's decorator parser followed the original behavior of TypeScript's experimental decorators feature, which only allowed decorators to come before the export keyword. However, the upcoming JavaScript decorators feature also allows decorators to come after the export keyword. And with TypeScript 5.0, TypeScript now also allows experimental decorators to come after the export keyword too. So esbuild now allows this as well:

  // This old syntax has always been permitted:
  @decorator export class Foo {}
  @decorator export default class Foo {}
  // This new syntax is now permitted too:
  export @​decorator class Foo {}
  export default @​decorator class Foo {}

  In addition, esbuild's decorator parser has been rewritten to fix several subtle and likely unimportant edge cases with esbuild's parsing of exports and decorators in TypeScript (e.g. TypeScript apparently does automatic semicolon insertion after interface and export interface but not after export default interface).

• Pretty-print decorators using the same whitespace as the original

  When printing code containing decorators, esbuild will now try to respect whether the original code contained newlines after the decorator or not. This can make generated code containing many decorators much more compact to read:

  // Original code
  class Foo {
    @a @b @c abc
    @x @y @z xyz
  }
  // Old output
  class Foo {
  @​a
  @​b
  @​c
  abc;
  @​x
  @​y
  @​z
  xyz;
  }
  // New output
  class Foo {
  @​a @​b @​c abc;
  @​x @​y @​z xyz;
  }

... (truncated)

Commits

• e97bd67 publish 0.19.8 to npm
• 65b3058 mention the treemap in the release notes (#2848)
• 16883d4 add whitespace change to release notes
• 7383d0d decorators: printing preserves newline-tail status
• 7edc83d reword an experimental decorators error message
• f3d5352 remove a now-unused field
• e755189 ts: forbid regular decorators on declare fields
• 69c9e7f allow decorators to come after export (#104)
• 7baefdb fix a panic with "export default interface\n"
• a8313d2 use "check" for decorator validation, not "guess"
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Issue Reference

In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide. We are closing this pull request for now but you can update the pull request description and reopen the pull request.
The check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (15125dc) 10.73% compared to head (c37a1ad) 10.73%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #185   +/-   ##
=======================================
  Coverage   10.73%   10.73%           
=======================================
  Files           6        6           
  Lines         326      326           
  Branches        8        8           
=======================================
  Hits           35       35           
  Misses        291      291           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dependabot]

Superseded by #195.