Sourced from @​esbuild/darwin-arm64's releases.

v0.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.

Sourced from @​esbuild/darwin-arm64's changelog.

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.

• a75b16e publish 0.19.4 to npm
• 65a4439 fix #3396: js decorator pretty-printing bugs
• 6ad177c add some js decorator printing tests
• 0e1696f ignore TP in data from caniuse-lite
• e7bf735 fix #3390: allow using disposable functions (#3391)
• 24bea0e update compat-table (note: regexp unicode 15.1)
• ea9c644 fix #3388: do something with pre-release versions
• See full diff in compare view

Sourced from @​esbuild/linux-arm64's releases.

v0.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.

Sourced from @​esbuild/linux-arm64's changelog.

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.

• a75b16e publish 0.19.4 to npm
• 65a4439 fix #3396: js decorator pretty-printing bugs
• 6ad177c add some js decorator printing tests
• 0e1696f ignore TP in data from caniuse-lite
• e7bf735 fix #3390: allow using disposable functions (#3391)
• 24bea0e update compat-table (note: regexp unicode 15.1)
• ea9c644 fix #3388: do something with pre-release versions
• See full diff in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions