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).
Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.
⚠️ This change may cause significant differences in your coverage results compared to Vitest v1. These changes are expected as coverage reporting is now more accurate. See vitest-dev/vitest#5423 for more details.
Previously, the location field pointed to the error location instead of the test location. Now it is aligned with jest and contains the line and column of a test function, but requires includeTaskLocation to be enabled.
dependabot[bot]
commented
1 month ago
Bumps the npm group with 6 updates in the / directory:
0.21.30.23.09.3.09.6.05.0.75.0.84.21.04.22.05.7.55.8.11.6.02.0.1Updates
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
eslintfrom 9.3.0 to 9.6.0Release notes
Sourced from eslint's releases.
... (truncated)
Changelog
Sourced from eslint's changelog.
... (truncated)
Commits
473d1bb9.6.0f435566Build: changelog update for 9.6.0b15ee30chore: upgrade@eslint/js@9.6.0 (#18632)d655503chore: package.json update for@eslint/jsrelease1613e2efix: Allow escaping characters in config patterns on Windows (#18628)13dbecddocs: Limit search to just docs (#18627)7c78ad9refactor: Use language.visitorKeys and check for non-JS SourceCode (#18625)e2b16e2feat: Implement feature flags (#18516)69ff64erefactor: Return value of applyInlineConfig() (#18623)375227fdocs: Update getting-started.md - add pnpm to init eslint config (#18599)Updates
rimraffrom 5.0.7 to 5.0.8Commits
0d83c125.0.888e632bdrop eol node 14f8c4b20DOC: missing punctuation & some grammar fixes (#307)dc3ffe5update tap, tshy, drop node 16 from ciUpdates
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 promises998d9cdv5.8.0d2f0778[Tests] handle more stack trace variation in Node v0.87ba18ac[New] addt.assertion7b39e14[Dev Deps] update@ljharb/eslint-config8d40837[Tests] strip node’s deprecation warnings732268b[Deps] updatearray.prototype.every,string.prototype.trimaa7de58[Tests] increase coverageUpdates
vitestfrom 1.6.0 to 2.0.1Release notes
Sourced from vitest's releases.