build(deps-dev): Bump esbuild from 0.17.11 to 0.17.12

[dependabot]

Bumps esbuild from 0.17.11 to 0.17.12.

Release notes

Sourced from esbuild's releases.

v0.17.12

• Fix a crash when parsing inline TypeScript decorators (#2991)

  Previously esbuild's TypeScript parser crashed when parsing TypeScript decorators if the definition of the decorator was inlined into the decorator itself:

  @(function sealed(constructor: Function) {
    Object.seal(constructor);
    Object.seal(constructor.prototype);
  })
  class Foo {}

  This crash was not noticed earlier because this edge case did not have test coverage. The crash is fixed in this release.

Changelog

Sourced from esbuild's changelog.

0.17.12

• Fix a crash when parsing inline TypeScript decorators (#2991)

  Previously esbuild's TypeScript parser crashed when parsing TypeScript decorators if the definition of the decorator was inlined into the decorator itself:

  @(function sealed(constructor: Function) {
    Object.seal(constructor);
    Object.seal(constructor.prototype);
  })
  class Foo {}

  This crash was not noticed earlier because this edge case did not have test coverage. The crash is fixed in this release.

Commits

• 495216d publish 0.17.12 to npm
• 1537025 close #2994: use deno types for type checking
• 4e96d42 update go 1.20.1 => 1.20.2
• 3b38ce3 fix #2991: crash with inline typescript decorator
• 0c8a0a9 mention "--watch=forever" in cli (#2987)
• 5ad10c6 fix colon in tests
• 44fd5ca Mention linked sourcemap support in cli help (#2982)
• 6729d46 fix colons after notes
• 14fb414 fix warnings about top-level css nesting
• See full diff 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 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)

[flexdevelopment]

lgtm 👍🏾

[codecov]

Codecov Report

Merging #224 (65b1f10) into main (0308409) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #224   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           65        65           
  Lines         5072      5072           
  Branches       466       466           
=========================================
  Hits          5072      5072           

Flag	Coverage Δ
node14	100.00% <ø> (ø)
node16	100.00% <ø> (ø)
node18	100.00% <ø> (ø)
node19	100.00% <ø> (ø)

Components	Coverage Δ
internal	100.00% <ø> (ø)
utils	100.00% <ø> (ø)

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d47fac8...65b1f10. Read the comment docs.

[github-actions]

This pull request has been automatically locked since there has not been any recent
activity after it was closed. Please open a new issue for related bugs or features. Be
sure to reference this issue.