Skip to content

Comments

Bump the npm_and_yarn group across 7 directories with 5 updates#94

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/custom_nodes/npm_and_yarn-58cab9383a
Open

Bump the npm_and_yarn group across 7 directories with 5 updates#94
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/custom_nodes/npm_and_yarn-58cab9383a

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 22, 2026

Bumps the npm_and_yarn group with 4 updates in the /custom_nodes directory: esbuild, tsup, js-yaml and tmp.
Bumps the npm_and_yarn group with 1 update in the /custom_nodes/examples/image_grid directory: esbuild.
Bumps the npm_and_yarn group with 1 update in the /custom_nodes/examples/make_uppercase directory: esbuild.
Bumps the npm_and_yarn group with 1 update in the /custom_nodes/examples/make_uppercase_vanilla directory: esbuild.
Bumps the npm_and_yarn group with 1 update in the /custom_nodes/examples/wikipedia_fetcher directory: esbuild.
Bumps the npm_and_yarn group with 1 update in the /custom_nodes/packages/node-utils directory: esbuild.
Bumps the npm_and_yarn group with 1 update in the /custom_nodes/packages/utility-nodes directory: esbuild.

Updates esbuild from 0.23.0 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: 2024

This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).

0.24.2

  • Fix regression with --define and import.meta (#4010, #4012, #4013)

    The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

    This fix was contributed by @​sapphi-red.

0.24.1

  • Allow es2024 as a target in tsconfig.json (#4004)

    TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

    {
  "compilerOptions": {
    "target": "ES2024"
  }
}

    As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

    This fix was contributed by @​billyjanitsch.

  • Allow automatic semicolon insertion after get/set

    This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

    class Foo {
  get
  *x() {}
  set
  *y() {}
}

    The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

  • Allow quoted property names in --define and --pure (#4008)

    The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

    

    • 






... (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 tsup from 8.2.3 to 8.3.5



Release notes

Sourced from tsup's releases.




v8.3.5


   🐞 Bug Fixes



    View changes on GitHub


v8.3.4


No significant changes


    View changes on GitHub


v8.3.3


No significant changes


    View changes on GitHub


v8.3.1


   🚀 Features



   🐞 Bug Fixes



    View changes on GitHub


v8.3.0


8.3.0 (2024-09-17)


Bug Fixes


    

  • fix experimentalDts file cleaning and watching (#1199) (76dc18b)
    • 



Features



v8.2.4


8.2.4 (2024-08-02)





... (truncated)





Commits






Updates js-yaml from 3.14.1 to 3.14.2



Changelog

Sourced from js-yaml's changelog.




[3.14.2] - 2025-11-15


Security


    

  • Backported v4.1.1 fix to v3
    • 



[4.1.1] - 2025-11-12


Security


    

  • Fix prototype pollution issue in yaml merge (<<) operator.
    • 



[4.1.0] - 2021-04-15


Added


    

  • Types are now exported as yaml.types.XXX.
    • 

  • Every type now has options property with original arguments kept as they were
(see yaml.types.int.options as an example).
    • 



Changed


    

  • Schema.extend() now keeps old type order in case of conflicts
(e.g. Schema.extend([ a, b, c ]).extend([ b, a, d ]) is now ordered as abcd instead of cbad).
    • 



[4.0.0] - 2021-01-03


Changed


    

  • Check migration guide to see details for all breaking changes.
    • 

  • Breaking: "unsafe" tags !!js/function, !!js/regexp, !!js/undefined are
moved to js-yaml-js-types package.
    • 

  • Breaking: removed safe* functions. Use load, loadAll, dump
instead which are all now safe by default.
    • 

  • yaml.DEFAULT_SAFE_SCHEMA and yaml.DEFAULT_FULL_SCHEMA are removed, use
yaml.DEFAULT_SCHEMA instead.
    • 

  • yaml.Schema.create(schema, tags) is removed, use schema.extend(tags) instead.
    • 

  • !!binary now always mapped to Uint8Array on load.
    • 

  • Reduced nesting of /lib folder.
    • 

  • Parse numbers according to YAML 1.2 instead of YAML 1.1 (01234 is now decimal,
0o1234 is octal, 1:23 is parsed as string instead of base60).
    • 

  • dump() no longer quotes :, [, ], (, ) except when necessary, #470, #557.
    • 

  • Line and column in exceptions are now formatted as (X:Y) instead of
at line X, column Y (also present in compact format), #332.
    • 

  • Code snippet created in exceptions now contains multiple lines with line numbers.
    • 

  • dump() now serializes undefined as null in collections and removes keys with
undefined in mappings, #571.
    • 

  • dump() with skipInvalid=true now serializes invalid items in collections as null.
    • 

  • Custom tags starting with ! are now dumped as !tag instead of !<!tag>, #576.
    • 

  • Custom tags starting with tag:yaml.org,2002: are now shorthanded using !!, #258.
    • 



Added


    

  • Added .mjs (es modules) support.
    • 

  • Added quotingType and forceQuotes options for dumper to configure
string literal style, #290, #529.
    • 

  • Added styles: { '!!null': 'empty' } option for dumper
(serializes { foo: null } as "foo: "), #570.
    • 






... (truncated)





Commits






Updates rollup from 4.19.1 to 4.58.0



Release notes

Sourced from rollup's releases.




v4.58.0


4.58.0


2026-02-20


Features


    

  • Also support __NO_SIDE_EFFECTS__ annotation before variable declarations declaring function expressions (#6272)
    • 



Pull Requests



v4.57.1


4.57.1


2026-01-30


Bug Fixes


    

  • Fix heap corruption issue in Windows (#6251)
    • 

  • Ensure exports of a dynamic import are fully included when called from a try...catch (#6254)
    • 



Pull Requests



v4.57.0


4.57.0


2026-01-27


Features


    

  • Add import attributes to all plugin hooks that did not provide them yet (#5700)
    • 






... (truncated)





Changelog

Sourced from rollup's changelog.




4.58.0


2026-02-20


Features


    

  • Also support __NO_SIDE_EFFECTS__ annotation before variable declarations declaring function expressions (#6272)
    • 



Pull Requests



4.57.1


2026-01-30


Bug Fixes


    

  • Fix heap corruption issue in Windows (#6251)
    • 

  • Ensure exports of a dynamic import are fully included when called from a try...catch (#6254)
    • 



Pull Requests



4.57.0


2026-01-27


Features


    

  • Add import attributes to all plugin hooks that did not provide them yet (#5700)
    • 

  • Deprecate returning import attributes from load or transform hooks as that will no longer be supported with rollup 5 (#5700)
    • 



Pull Requests





... (truncated)





Commits

    

  • 33f39c1 4.58.0
    • 

  • b61c408 forward NO_SIDE_EFFECTS annotations to function expressions in variable decla...
    • 

  • 7f00689 Extend agent instructions
    • 

  • e7b2b85 chore(deps): lock file maintenance (#6270)
    • 

  • 2aa5da9 fix(deps): update minor/patch updates (#6267)
    • 

  • 4319837 chore(deps): update dependency lru-cache to v11 (#6269)
    • 

  • c3b6b4b chore(deps): update dependency eslint-plugin-unicorn to v63 (#6268)
    • 

  • 8653dd7 fix(deps): update minor/patch updates (#6263)
    • 

  • c49fba1 chore(deps): lock file maintenance (#6265)
    • 

  • 74559c0 Avoid unnecessary cloning of the code string (#6262)
    • 

  • Additional commits viewable in compare view
    • 






Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for rollup since your current version.





Install script changes

This version modifies prepare script that runs during installation. Review the package contents before updating.






Removes tmp


Updates esbuild from 0.12.29 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: 2024


This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).


0.24.2


    

  • 

    Fix regression with --define and import.meta (#4010, #4012, #4013)
    

    The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.
    

    This fix was contributed by @​sapphi-red.
    

    • 



0.24.1


    

  • 

    Allow es2024 as a target in tsconfig.json (#4004)
    

    TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:
    

    {
  "compilerOptions": {
    "target": "ES2024"
  }
}
    

    As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.
    

    This fix was contributed by @​billyjanitsch.
    

    • 

  • 

    Allow automatic semicolon insertion after get/set
    

    This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:
    

    class Foo {
  get
  *x() {}
  set
  *y() {}
}
    

    The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.
    

    • 

  • 

    Allow quoted property names in --define and --pure (#4008)
    

    The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:
    

    

    • 






... (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 from 0.12.29 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: 2024


This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).


0.24.2


    

  • 

    Fix regression with --define and import.meta (#4010, #4012, #4013)
    

    The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.
    

    This fix was contributed by @​sapphi-red.
    

    • 



0.24.1


    

  • 

    Allow es2024 as a target in tsconfig.json (#4004)
    

    TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:
    

    {
  "compilerOptions": {
    "target": "ES2024"
  }
}
    

    As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.
    

    This fix was contributed by @​billyjanitsch.
    

    • 

  • 

    Allow automatic semicolon insertion after get/set
    

    This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:
    

    class Foo {
  get
  *x() {}
  set
  *y() {}
}
    

    The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.
    

    • 

  • 

    Allow quoted property names in --define and --pure (#4008)
    

    The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:
    

    

    • 






... (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 from 0.12.29 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: 2024


This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).


0.24.2


    

  • 

    Fix regression with --define and import.meta (#4010, #4012, #4013)
    

    The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.
    

    This fix was contributed by @​sapphi-red.
    

    • 



0.2...

Description has been truncated

    

  
  



      


          

          
  
  

    
  
    
    

  

  

  



                    

          
        





  





    



      

  
        

  

      

  
  

  
          

  

    

      


  

      
        @dependabot
  




      

        
          Bump the npm_and_yarn group across 7 directories with 5 updates
        

          
                        
      


      

        

    
    
    

  

    


      


      

        

          

    
    
    

  

  

    
  



        

      


      

        
          472997c
        
      

    

  

    

      
Bumps the npm_and_yarn group with 4 updates in the /custom_nodes directory: [esbuild](https://github.com/evanw/esbuild), [tsup](https://github.com/egoist/tsup), [js-yaml](https://github.com/nodeca/js-yaml) and [tmp](https://github.com/raszi/node-tmp).
Bumps the npm_and_yarn group with 1 update in the /custom_nodes/examples/image_grid directory: [esbuild](https://github.com/evanw/esbuild).
Bumps the npm_and_yarn group with 1 update in the /custom_nodes/examples/make_uppercase directory: [esbuild](https://github.com/evanw/esbuild).
Bumps the npm_and_yarn group with 1 update in the /custom_nodes/examples/make_uppercase_vanilla directory: [esbuild](https://github.com/evanw/esbuild).
Bumps the npm_and_yarn group with 1 update in the /custom_nodes/examples/wikipedia_fetcher directory: [esbuild](https://github.com/evanw/esbuild).
Bumps the npm_and_yarn group with 1 update in the /custom_nodes/packages/node-utils directory: [esbuild](https://github.com/evanw/esbuild).
Bumps the npm_and_yarn group with 1 update in the /custom_nodes/packages/utility-nodes directory: [esbuild](https://github.com/evanw/esbuild).


Updates `esbuild` from 0.23.0 to 0.25.0
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md)
- [Commits](evanw/esbuild@v0.23.0...v0.25.0)

Updates `tsup` from 8.2.3 to 8.3.5
- [Release notes](https://github.com/egoist/tsup/releases)
- [Commits](egoist/tsup@v8.2.3...v8.3.5)

Updates `js-yaml` from 3.14.1 to 3.14.2
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](nodeca/js-yaml@3.14.1...3.14.2)

Updates `rollup` from 4.19.1 to 4.58.0
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.19.1...v4.58.0)

Removes `tmp`

Updates `esbuild` from 0.12.29 to 0.25.0
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md)
- [Commits](evanw/esbuild@v0.23.0...v0.25.0)

Updates `esbuild` from 0.12.29 to 0.25.0
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md)
- [Commits](evanw/esbuild@v0.23.0...v0.25.0)

Updates `esbuild` from 0.12.29 to 0.25.0
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md)
- [Commits](evanw/esbuild@v0.23.0...v0.25.0)

Updates `esbuild` from 0.12.29 to 0.25.0
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md)
- [Commits](evanw/esbuild@v0.23.0...v0.25.0)

Updates `esbuild` from 0.23.1 to 0.27.3
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md)
- [Commits](evanw/esbuild@v0.23.0...v0.25.0)

Updates `esbuild` from 0.23.1 to 0.27.3
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md)
- [Commits](evanw/esbuild@v0.23.0...v0.25.0)

---
updated-dependencies:
- dependency-name: esbuild
  dependency-version: 0.25.0
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: tsup
  dependency-version: 8.3.5
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: js-yaml
  dependency-version: 3.14.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: rollup
  dependency-version: 4.58.0
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: tmp
  dependency-version: 
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-version: 0.25.0
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-version: 0.25.0
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-version: 0.25.0
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-version: 0.25.0
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-version: 0.27.3
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: esbuild
  dependency-version: 0.27.3
  dependency-type: direct:development
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>

    







  








      

  
            

    

      
    

    


      


          @dependabot
dependabot
bot



            added
      

  dependencies

  Pull requests that update a dependency file

      

  javascript

  Pull requests that update javascript code

  labels


      Feb 22, 2026

    

  



  

  

    
  


  

      


    @dependabot
dependabot
bot


    mentioned this pull request
    
      Feb 22, 2026
    





  


  

      
   Closed

  







  













  
  

    

      

  










  








  
      

  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment


  










      

  

    
    

    

  

    Reviewers
  


    

    No reviews






    
    

    

  


      
  

    Assignees
  



        


    No one assigned







      


  


  

    Labels
  



    

      

    dependencies

  Pull requests that update a dependency file
  

    javascript

  Pull requests that update javascript code








      

  

    

        

    Projects
  


        




    None yet




  



      


  

    
  

    Milestone
  


      No milestone





    
      
          


  

    

      
        

          
  

    Development
  



            


Successfully merging this pull request may close these issues.





  
  



      
    

  




      

    

  
      

  

    

      0 participants