Bump the npm_and_yarn group with 3 updates

[dependabot]

Bumps the npm_and_yarn group with 3 updates: esbuild, esbuild-loader and esbuild-plugin-browserslist.

Updates esbuild from 0.16.17 to 0.25.0

Release notes

Sourced from esbuild's releases.

v0.25.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.24.0 or ~0.24.0. See npm's documentation about semver for more information.

• Restrict access to esbuild's development server (GHSA-67mh-4wv8-2f99)

  This change addresses esbuild's first security vulnerability report. Previously esbuild set the Access-Control-Allow-Origin header to * to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in the report.

  Starting with this release, CORS will now be disabled, and requests will now be denied if the host does not match the one provided to --serve=. The default host is 0.0.0.0, which refers to all of the IP addresses that represent the local machine (e.g. both 127.0.0.1 and 192.168.0.1). If you want to customize anything about esbuild's development server, you can put a proxy in front of esbuild and modify the incoming and/or outgoing requests.

  In addition, the serve() API call has been changed to return an array of hosts instead of a single host string. This makes it possible to determine all of the hosts that esbuild's development server will accept.

  Thanks to @​sapphi-red for reporting this issue.

• Delete output files when a build fails in watch mode (#3643)

  It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.

• Fix correctness issues with the CSS nesting transform (#3620, #3877, #3933, #3997, #4005, #4037, #4038)

  This release fixes the following problems:

  • Naive expansion of CSS nesting can result in an exponential blow-up of generated CSS if each nesting level has multiple selectors. Previously esbuild sometimes collapsed individual nesting levels using :is() to limit expansion. However, this collapsing wasn't correct in some cases, so it has been removed to fix correctness issues.

    /* Original code */
    .parent {
      > .a,
      > .b1 > .b2 {
        color: red;
      }
    }
    /* Old output (with --supported:nesting=false) */
    .parent > :is(.a, .b1 > .b2) {
    color: red;
    }
    /* New output (with --supported:nesting=false) */
    .parent > .a,
    .parent > .b1 > .b2 {
    color: red;
    }

    Thanks to @​tim-we for working on a fix.

  • The & CSS nesting selector can be repeated multiple times to increase CSS specificity. Previously esbuild ignored this possibility and incorrectly considered && to have the same specificity as &. With this release, this should now work correctly:

    /* Original code (color should be red) */

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2023

This changelog documents all esbuild versions published in the year 2023 (versions 0.16.13 through 0.19.11).

0.19.11

• Fix TypeScript-specific class transform edge case (#3559)

  The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

  // Original code
  class Foo extends Bar {
    #private = 1;
    public: any;
    constructor() {
      super();
    }
  }
  // Old output (with esbuild v0.19.9)
  class Foo extends Bar {
  constructor() {
  super();
  this.#private = 1;
  }
  #private;
  }
  // Old output (with esbuild v0.19.10)
  class Foo extends Bar {
  constructor() {
  this.#private = 1;
  super();
  }
  #private;
  }
  // New output
  class Foo extends Bar {
  #private = 1;
  constructor() {
  super();
  }
  }

• Minifier: allow reording a primitive past a side-effect (#3568)

  The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

... (truncated)

Commits

• e9174d6 publish 0.25.0 to npm
• c27dbeb fix hosts in plugin-tests.js
• 6794f60 fix hosts in node-unref-tests.js
• de85afd Merge commit from fork
• da1de1b fix #4065: bitwise operators can return bigints
• f4e9d19 switch case liveness: default is always last
• 7aa47c3 fix #4028: minify live/dead switch cases better
• 22ecd30 minify: more constant folding for strict equality
• 4cdf03c fix #4053: reordering of .tsx in node_modules
• dc71977 fix #3692: 0 now picks a random ephemeral port
• Additional commits viewable in compare view

Updates esbuild-loader from 2.21.0 to 4.3.0

Release notes

Sourced from esbuild-loader's releases.

v4.3.0

4.3.0 (2025-02-11)

Features

• upgrade esbuild to ^0.25 (#382) (42ec34f)

v4.2.2

4.2.2 (2024-07-16)

Bug Fixes

• tsconfig.json edge-cases in dependencies (#377) (e252654)

v4.2.1

4.2.1 (2024-07-15)

Bug Fixes

• explicitly import webpack as type (3dd1107)

v4.2.0

4.2.0 (2024-06-17)

Features

• upgrade esbuild to ^0.21 (#374) (53a5966)

v4.1.0

4.1.0 (2024-03-08)

Features

• enable dynamic-imports by default (#361) (7b948ef)
• upgrade esbuild to 0.20 (#362) (58d5573)

v4.0.3

4.0.3 (2024-01-23)

Bug Fixes

• handle empty build (#357) (3bddb9d)
• types: support NodeNext (037bb99), closes #342

... (truncated)

Commits

• 42ec34f feat: upgrade esbuild to ^0.25 (#382)
• e252654 fix: tsconfig.json edge-cases in dependencies (#377)
• 6592c42 chore: add webpack env var to dev env
• 3dd1107 fix: explicitly import webpack as type
• a89e486 style: add tsconfig.json lib for type check to pass
• 0e623be style: lint fix
• b5ee6a4 ci: run on master
• 53a56a5 chore: add logo
• 507bc87 chore: upgrade test tools
• 5945c18 chore: upgrade node
• Additional commits viewable in compare view

Updates esbuild-plugin-browserslist from 0.6.0 to 0.16.0

Release notes

Sourced from esbuild-plugin-browserslist's releases.

esbuild-plugin-browserslist: v0.16.0

0.16.0 (2025-02-10)

⚠ BREAKING CHANGES

• update esbuild@~0.25.0 (#236)

Features

• update esbuild@~0.25.0 (#236) (222d414)

esbuild-plugin-browserslist: v0.15.0

0.15.0 (2024-10-01)

⚠ BREAKING CHANGES

• deps: bump all including esbuild 0.24.x (#215)

Features

• deps: bump all including esbuild 0.24.x (#215) (9431519)

esbuild-plugin-browserslist: v0.14.0

0.14.0 (2024-07-08)

⚠ BREAKING CHANGES

• deps: support esbuild 0.23 (#198)

Features

• deps: support esbuild 0.23 (#198) (4264416)

esbuild-plugin-browserslist: v0.13.0

0.13.0 (2024-07-02)

⚠ BREAKING CHANGES

• deps: support esbuild 0.22

Features

• deps: support esbuild 0.22 (e51e017)

esbuild-plugin-browserslist: v0.12.1

0.12.1 (2024-06-04)

... (truncated)

Changelog

Sourced from esbuild-plugin-browserslist's changelog.

0.16.0 (2025-02-10)

⚠ BREAKING CHANGES

• update esbuild@~0.25.0 (#236)

Features

• update esbuild@~0.25.0 (#236) (222d414)

0.15.0 (2024-10-01)

⚠ BREAKING CHANGES

• deps: bump all including esbuild 0.24.x (#215)

Features

• deps: bump all including esbuild 0.24.x (#215) (9431519)

0.14.0 (2024-07-08)

⚠ BREAKING CHANGES

• deps: support esbuild 0.23 (#198)

Features

• deps: support esbuild 0.23 (#198) (4264416)

0.13.0 (2024-07-02)

⚠ BREAKING CHANGES

• deps: support esbuild 0.22

Features

• deps: support esbuild 0.22 (e51e017)

0.12.1 (2024-06-04)

Bug Fixes

• deps: bump the all group with 4 updates (#190) (a5380a6)

... (truncated)

Commits

• 2961895 chore(main): release esbuild-plugin-browserslist 0.16.0 (#237)
• 94103a7 chore(deps-dev): update all
• 222d414 feat!: update esbuild@~0.25.0 (#236)
• ff388aa chore(deps-dev): bump the all group with 9 updates (#235)
• 30d159a chore(deps-dev): bump the all group with 8 updates (#234)
• 91d339b chore(deps-dev): bump the all group with 13 updates (#233)
• 7d7a448 chore(deps): bump the all group with 9 updates (#232)
• bfee16c chore(deps): bump nanoid from 3.3.7 to 3.3.8 in the npm_and_yarn group (#231)
• f391a19 chore(deps): bump the all group with 6 updates (#230)
• c00f7c2 chore(deps-dev): bump the all group with 9 updates (#229)
• 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 <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
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[netlify]

✅ Deploy Preview for splendorous-kataifi-9ae281 ready!

Name	Link
🔨 Latest commit	6d6ea44
🔍 Latest deploy log	https://app.netlify.com/sites/splendorous-kataifi-9ae281/deploys/67ae0d4c5bf19d0008689a4f
😎 Deploy Preview	https://deploy-preview-216--splendorous-kataifi-9ae281.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.