build(deps-dev): bump esbuild from 0.14.49 to 0.19.9

[dependabot]

Bumps esbuild from 0.14.49 to 0.19.9.

Release notes

Sourced from esbuild's releases.

v0.19.9

• Add support for transforming new CSS gradient syntax for older browsers

  The specification called CSS Images Module Level 4 introduces new CSS gradient syntax for customizing how the browser interpolates colors in between color stops. You can now control the color space that the interpolation happens in as well as (for "polar" color spaces) control whether hue angle interpolation happens clockwise or counterclockwise. You can read more about this in Mozilla's blog post about new CSS gradient features.

  With this release, esbuild will now automatically transform this syntax for older browsers in the target list. For example, here's a gradient that should appear as a rainbow in a browser that supports this new syntax:

  /* Original code */
  .rainbow-gradient {
    width: 100px;
    height: 100px;
    background: linear-gradient(in hsl longer hue, #7ff, #77f);
  }
  /* New output (with --target=chrome99) */
  .rainbow-gradient {
  width: 100px;
  height: 100px;
  background:
  linear-gradient(
  #77ffff,
  #77ffaa 12.5%,
  #77ff80 18.75%,
  #84ff77 21.88%,
  #99ff77 25%,
  #eeff77 37.5%,
  #fffb77 40.62%,
  #ffe577 43.75%,
  #ffbb77 50%,
  #ff9077 56.25%,
  #ff7b77 59.38%,
  #ff7788 62.5%,
  #ff77dd 75%,
  #ff77f2 78.12%,
  #f777ff 81.25%,
  #cc77ff 87.5%,
  #7777ff);
  }

  You can now use this syntax in your CSS source code and esbuild will automatically convert it to an equivalent gradient for older browsers. In addition, esbuild will now also transform "double position" and "transition hint" syntax for older browsers as appropriate:

  /* Original code */
  .stripes {
    width: 100px;
    height: 100px;
    background: linear-gradient(#e65 33%, #ff2 33% 67%, #99e 67%);
  }

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2022

This changelog documents all esbuild versions published in the year 2022 (versions 0.14.11 through 0.16.12).

0.16.12

• Loader defaults to js for extensionless files (#2776)

  Certain packages contain files without an extension. For example, the yargs package contains the file yargs/yargs which has no extension. Node, Webpack, and Parcel can all understand code that imports yargs/yargs because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for "" (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this:

  • CLI:

    esbuild --bundle --loader:=css
    

  • JS:

    esbuild.build({
      bundle: true,
      loader: { '': 'css' },
    })

  • Go:

    api.Build(api.BuildOptions{
      Bundle: true,
      Loader: map[string]api.Loader{"": api.LoaderCSS},
    })

  In addition, the "type" field in package.json files now only applies to files with an explicit .js, .jsx, .ts, or .tsx extension. Previously it was incorrectly applied by esbuild to all files that had an extension other than .mjs, .mts, .cjs, or .cts including extensionless files. So for example an extensionless file in a "type": "module" package is now treated as CommonJS instead of ESM.

0.16.11

• Avoid a syntax error in the presence of direct eval (#2761)

  The behavior of nested function declarations in JavaScript depends on whether the code is run in strict mode or not. It would be problematic if esbuild preserved nested function declarations in its output because then the behavior would depend on whether the output was run in strict mode or not instead of respecting the strict mode behavior of the original source code. To avoid this, esbuild transforms nested function declarations to preserve the intended behavior of the original source code regardless of whether the output is run in strict mode or not:

  // Original code
  if (true) {
    function foo() {}
    console.log(!!foo)
    foo = null
    console.log(!!foo)
  }

... (truncated)

Commits

• 9edc9d4 publish 0.19.9 to npm
• 791619e release notes: link to gradient tests
• 83b4171 css: implement lowering of gradient syntax
• 4a3b265 css: fix calc() inlining whitespace bug
• 90989ec remove a stray log statement
• f260285 css gradients: handle color transition hints
• e4c55af css gradients: lower colors, fix double positions
• a389c52 css: add lab() + lch() + oklab() + oklch()
• b837f21 css: avoid overwriting manual fallback colors
• 824ede6 css: simplify color() duplication fallback logic
• 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)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
website	❌ Failed (Inspect)			Dec 11, 2023 4:08am

[dependabot]

Superseded by #388.