Bump github.com/evanw/esbuild from 0.14.21 to 0.14.23 in /hashira-web

[dependabot]

Bumps github.com/evanw/esbuild from 0.14.21 to 0.14.23.

Release notes

Sourced from github.com/evanw/esbuild's releases.

v0.14.23

• Update feature database to indicate that node 16.14+ supports import assertions (#2030)

  Node versions 16.14 and above now support import assertions according to these release notes. This release updates esbuild's internal feature compatibility database with this information, so esbuild no longer strips import assertions with --target=node16.14:

  // Original code
  import data from './package.json' assert { type: 'json' }
  console.log(data)
  // Old output (with --target=node16.14)
  import data from "./package.json";
  console.log(data);
  // New output (with --target=node16.14)
  import data from "./package.json" assert { type: "json" };
  console.log(data);

• Basic support for CSS @layer rules (#2027)

  This adds basic parsing support for a new CSS feature called @layer that changes how the CSS cascade works. Adding parsing support for this rule to esbuild means esbuild can now minify the contents of @layer rules:

  /* Original code */
  @layer a {
    @layer b {
      div {
        color: yellow;
        margin: 0.0px;
      }
    }
  }
  /* Old output (with --minify) */
  @​layer a{@​layer b {div {color: yellow; margin: 0px;}}}
  /* New output (with --minify) */
  @​layer a.b{div{color:#ff0;margin:0}}

  You can read more about @layer here:

  • Documentation: https://developer.mozilla.org/en-US/docs/Web/CSS/@​layer
  • Motivation: https://developer.chrome.com/blog/cascade-layers/

  Note that the support added in this release is only for parsing and printing @layer rules. The bundler does not yet know about these rules and bundling with @layer may result in behavior changes since these new rules have unusual ordering constraints that behave differently than all other CSS rules. Specifically the order is derived from the first instance while with every other CSS rule, the order is derived from the last instance.

v0.14.22

• Preserve whitespace for token lists that look like CSS variable declarations (#2020)

... (truncated)

Changelog

Sourced from github.com/evanw/esbuild's changelog.

0.14.23

• Update feature database to indicate that node 16.14+ supports import assertions (#2030)

  Node versions 16.14 and above now support import assertions according to these release notes. This release updates esbuild's internal feature compatibility database with this information, so esbuild no longer strips import assertions with --target=node16.14:

  // Original code
  import data from './package.json' assert { type: 'json' }
  console.log(data)
  // Old output (with --target=node16.14)
  import data from "./package.json";
  console.log(data);
  // New output (with --target=node16.14)
  import data from "./package.json" assert { type: "json" };
  console.log(data);

• Basic support for CSS @layer rules (#2027)

  This adds basic parsing support for a new CSS feature called @layer that changes how the CSS cascade works. Adding parsing support for this rule to esbuild means esbuild can now minify the contents of @layer rules:

  /* Original code */
  @layer a {
    @layer b {
      div {
        color: yellow;
        margin: 0.0px;
      }
    }
  }
  /* Old output (with --minify) */
  @​layer a{@​layer b {div {color: yellow; margin: 0px;}}}
  /* New output (with --minify) */
  @​layer a.b{div{color:#ff0;margin:0}}

  You can read more about @layer here:

  • Documentation: https://developer.mozilla.org/en-US/docs/Web/CSS/@​layer
  • Motivation: https://developer.chrome.com/blog/cascade-layers/

  Note that the support added in this release is only for parsing and printing @layer rules. The bundler does not yet know about these rules and bundling with @layer may result in behavior changes since these new rules have unusual ordering constraints that behave differently than all other CSS rules. Specifically the order is derived from the first instance while with every other CSS rule, the order is derived from the last instance.

0.14.22

... (truncated)

Commits

• bf341f7 publish 0.14.23 to npm
• 157a4c0 point out error handler in resolve debug message
• 1ec2671 new message when "type" should be "types" (#395)
• 988aab7 fix #2030: keep import assertions with node 16.14+
• 9a96435 move comment to correct block
• 4ec22ea Remove extra len(b.Properties) > 0 check (#2025)
• 2734bbf fix #2027: parser support for css @layer rules
• 914fb09 Update CHANGELOG.md
• b7dbea2 chore: gitignore editor tmp dir & lib npm with private (#2022)
• b26003f publish 0.14.22 to npm
• 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 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)