Update esbuild → 0.19.4 (unknown)

[depfu]

---

Welcome to Depfu 👋

This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

Let us know if you have any questions. Thanks so much for giving Depfu a try!

---

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ esbuild (^0.18.12 → ^0.19.4) · Repo · Changelog

Release Notes

0.19.4

• Fix printing of JavaScript decorators in tricky cases (#3396)

  This release fixes some bugs where esbuild's pretty-printing of JavaScript decorators could incorrectly produced code with a syntax error. The problem happened because esbuild sometimes substitutes identifiers for other expressions in the pretty-printer itself, but the decision about whether to wrap the expression or not didn't account for this. Here are some examples:

  // Original code
  import { constant } from './constants.js'
  import { imported } from 'external'
  import { undef } from './empty.js'
  class Foo {
    @constant()
    @imported()
    @undef()
    foo
  }
  // Old output (with --bundle --format=cjs --packages=external --minify-syntax)
  
  var import_external = require("external");
  
  var Foo = class {
  
  @123()
  
  @(0, import_external.imported)()
  
  @(void 0)()
  
  foo;
  
  };
  // New output (with --bundle --format=cjs --packages=external --minify-syntax)
  
  var import_external = require("external");
  
  var Foo = class {
  
  @(123())
  
  @((0, import_external.imported)())
  
  @((void 0)())
  
  foo;
  
  };

• Allow pre-release versions to be passed to target (#3388)

  People want to be able to pass version numbers for unreleased versions of node (which have extra stuff after the version numbers) to esbuild's target setting and have esbuild do something reasonable with them. These version strings are of course not present in esbuild's internal feature compatibility table because an unreleased version has not been released yet (by definition). With this release, esbuild will now attempt to accept these version strings passed to target and do something reasonable with them.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 7 commits:

• publish 0.19.4 to npm
• fix #3396: js decorator pretty-printing bugs
• add some js decorator printing tests
• ignore `TP` in data from caniuse-lite
• fix #3390: allow `using` disposable functions (#3391)
• update `compat-table` (note: regexp unicode 15.1)
• fix #3388: do something with pre-release versions

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #26.