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.22.0 or ~0.22.0. See npm's documentation about semver for more information.
Revert the recent change to avoid bundling dependencies for node (#3819)
This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.
I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.
In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.
When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:
// Original code
<Foo>
<Bar />
</Foo>
// Old output (with --jsx=preserve)
<Foo><Bar /></Foo>;
// New output (with --jsx=preserve)
<Foo>
<Bar />
</Foo>;
v0.22.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.21.0 or ~0.21.0. See npm's documentation about semver for more information.
This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.
With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.
The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).
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.22.0 or ~0.22.0. See npm's documentation about semver for more information.
Revert the recent change to avoid bundling dependencies for node (#3819)
This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.
I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.
In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.
When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:
// Original code
<Foo>
<Bar />
</Foo>
// Old output (with --jsx=preserve)
<Foo><Bar /></Foo>;
// New output (with --jsx=preserve)
<Foo>
<Bar />
</Foo>;
0.22.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.21.0 or ~0.21.0. See npm's documentation about semver for more information.
This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.
With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.
The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).
Provide Dirent or Stats object as second argument to filter
4.3
Return boolean indicating whether the path was fully removed
Add filter option
bin: add --verbose, -v to print files as they are deleted
bin: add --no-verbose, -V to not print files as they are deleted
bin: add -i --interactive to be prompted on each deletion
bin: add -I --no-interactive to not be prompted on each
deletion
4.3.1 Fixed inappropriately following symbolic links to
directories
v4.2
Brought back glob support, using the new and improved glob v9
v4.1
Improved hybrid module with no need to look at the .default
dangly bit. .default preserved as a reference to rimraf
for compatibility with anyone who came to rely on it in v4.0.
Accept and ignore -rf and -fr arguments to the bin.
v4.0
Remove glob dependency entirely. This library now only
accepts actual file and folder names to delete.
Accept array of paths or single path.
Windows performance and reliability improved.
All strategies separated into explicitly exported methods.
Drop support for Node.js below version 14
rewrite in TypeScript
ship CJS/ESM hybrid module
Error on unknown arguments to the bin. (Previously they were
silently ignored.)
Bumps the npm group with 7 updates in the / directory:
0.21.30.23.03.13.03.13.19.3.09.7.05.0.76.0.14.21.04.22.05.7.55.8.11.6.02.0.3Updates
esbuildfrom 0.21.3 to 0.23.0Release notes
Sourced from esbuild's releases.
... (truncated)
Changelog
Sourced from esbuild's changelog.
... (truncated)
Commits
9d50680publish 0.23.0 to npmac7fd04Revert "fix #1874: node defaults to--packages=external" (#3820)626ac2cfix #3818: preserve collapsed jsx whitespace7c2eb2ehashbang syntax is part of es202380c6e6epublish 0.22.0 to npm196dcadfix #1874: node defaults to--packages=external3f57db8release notes for #353991663dbProvide API to create a custom esbuild CLI with plugins (#3539)e01c0e0also mention #3665 in release notes65711b3release notes for #3674Updates
winstonfrom 3.13.0 to 3.13.1Release notes
Sourced from winston's releases.
Commits
7d7f9d33.13.11b3a500revert to rimraf 5.0.1, last known version to work with node 18 for nowb56117eMerge branch 'master' of github.com:winstonjs/winstona5853b5Update dependencies93b52acBump@types/nodefrom 20.12.7 to 20.14.10 (#2483)33611c9Bump mocha from 10.3.0 to 10.6.0 (#2484)4aa6550Bump@babel/preset-envfrom 7.24.0 to 7.24.7 (#2475)7f5f014Update minimum version logform (#2472)debf4faAdd Parseable transport (#2466)d567c57chore(docs): Update w/ MySQL transport (#2456)Updates
eslintfrom 9.3.0 to 9.7.0Release notes
Sourced from eslint's releases.
... (truncated)
Changelog
Sourced from eslint's changelog.
... (truncated)
Commits
05ab8129.7.01917cd3Build: changelog update for 9.7.0793b718chore: upgrade@eslint/js@9.7.0 (#18680)7ed6f9achore: package.json update for@eslint/jsrelease14e9f81fix: destructuring in catch clause inno-unused-vars(#18636)7bcda76refactor: Add type references (#18652)51bf57cchore: add tech sponsors through actions (#18624)9f416dbdocs: Add Powered by Algolia label to the search. (#18633)6320732refactor: don't useparentproperty inNodeEventGenerator(#18653)7bd9839feat: add support for es2025 duplicate named capturing groups (#18630)Updates
rimraffrom 5.0.7 to 6.0.1Changelog
Sourced from rimraf's changelog.
... (truncated)
Commits
21560c76.0.1d3881adload version with package-json-from-dist6de86bffeat: add --version flag for CLI49e1923chore: add/.tapto .gitignore90d1feb6.0.09b2a2b1drop dead node versions546c9ec5.0.9043338arestore support for dead node versions0d83c125.0.888e632bdrop eol node 14Updates
selenium-webdriverfrom 4.21.0 to 4.22.0Release notes
Sourced from selenium-webdriver's releases.
... (truncated)
Commits
c5f3146[build] Prepare for release of Selenium 4.22.0 (#14163)2a7ddf1[java] use java.nio to check files #1408800c4f60[build] create github workflow for updating documentation6704db0[java] minor performance improvements and code cleanup (#14054)aca918bEdgeOptions.useWebView to return "this" (#14157)0814580[build] create a stage release workflow for after the pre-release PR (#14122)8b56711[py] remove desired capabilities argument for Webkitgtk (#14128)078ff3b[js] Fix locate nodes BiDi test (#14140)f8db820[rb] remove guards from test for fixed edge bug8960ff0[bidi][js] Add high-level logging API (#14135)Updates
tapefrom 5.7.5 to 5.8.1Changelog
Sourced from tape's changelog.
Commits
e52bb18v5.8.17c84990[meta] fix URLs2ad86d4[Fix]assertion: pass through assertion return value, for promisesLooks like these dependencies are updatable in another way, so this is no longer needed.