Sourced from ava's releases.
v6.4.0
What's Changed
- AVA is now tested with Node.js 24 (but no longer v23) avajs/ava#3379
- We're now publishing to npm with provenance attestations avajs/ava#3385
Interactive watch mode filters
@mmuletdid fantastic work to spearhead interactive watch mode filters. You can now filter test files by glob patterns, and tests by matching their titles. It's just like you already could from the CLI itself, but now without exiting AVA 🚀 avajs/ava#3372As part of this work we've removed the "sticky"
.only()behavior avajs/ava#3381Examples
We've been remiss in merging avajs/ava#3335 which updates the examples to use AVA 6. It's done now, examples are up to date and it's all due to
@tommy-mitchell👏New Contributors
@mmuletmade their first contribution in avajs/ava#3372@kebbellmade their first contribution in avajs/ava#3348Full Changelog: https://github.com/avajs/ava/compare/v6.3.0...v6.4.0
372c241
6.4.005ead28
Update release process & maintaining notes859f3ff
Update examples to use AVA 6eb2b48d
Update XO & other dependencies50e02d5
Remove compiler option override needed for TypeScript 4.x57a3bbe
Implement file globbing and test matching within watch mode29cb29a
Remove special .only() behavior in watch mode36934b2
Fix error handling in watcher tests31a1262
Test with Node.js 24, remove v23 test runsa6f42ea
Upgrade @ava/test to 6.3.0Sourced from esbuild's releases.
v0.25.6
Fix a memory leak when
cancel()is used on a build context (#4231)Calling
rebuild()followed bycancel()in rapid succession could previously leak memory. The bundler uses a producer/consumer model internally, and the resource leak was caused by the consumer being termianted while there were still remaining unreceived results from a producer. To avoid the leak, the consumer now waits for all producers to finish before terminating.Support empty
:is()and:where()syntax in CSS (#4232)Previously using these selectors with esbuild would generate a warning. That warning has been removed in this release for these cases.
Improve tree-shaking of
trystatements in dead code (#4224)With this release, esbuild will now remove certain
trystatements if esbuild considers them to be within dead code (i.e. code that is known to not ever be evaluated). For example:// Original code return 'foo' try { return 'bar' } catch {}// Old output (with --minify) return"foo";try{return"bar"}catch{}
// New output (with --minify) return"foo";
Consider negated bigints to have no side effects
While esbuild currently considers
1,-1, and1nto all have no side effects, it didn't previously consider-1nto have no side effects. This is because esbuild does constant folding with numbers but not bigints. However, it meant that unused negative bigint constants were not tree-shaken. With this release, esbuild will now consider these expressions to also be side-effect free:// Original code let a = 1, b = -1, c = 1n, d = -1n// Old output (with --bundle --minify) (()=>{var n=-1n;})();
// New output (with --bundle --minify) (()=>{})();
Support a configurable delay in watch mode before rebuilding (#3476, #4178)
The
watch()API now takes adelayoption that lets you add a delay (in milliseconds) before rebuilding when a change is detected in watch mode. If you use a tool that regenerates multiple source files very slowly, this should make it more likely that esbuild's watch mode won't generate a broken intermediate build before the successful final build. This option is also available via the CLI using the--watch-delay=flag.This should also help avoid confusion about the
watch()API's options argument. It was previously empty to allow for future API expansion, which caused some people to think that the documentation was missing. It's no longer empty now that thewatch()API has an option.Allow mixed array for
entryPointsAPI option (#4223)The TypeScript type definitions now allow you to pass a mixed array of both string literals and object literals to the
entryPointsAPI option, such as['foo.js', { out: 'lib', in: 'bar.js' }]. This was always possible to do in JavaScript but the TypeScript type definitions were previously too restrictive.
... (truncated)
Sourced from esbuild's changelog.
0.25.6
Fix a memory leak when
cancel()is used on a build context (#4231)Calling
rebuild()followed bycancel()in rapid succession could previously leak memory. The bundler uses a producer/consumer model internally, and the resource leak was caused by the consumer being termianted while there were still remaining unreceived results from a producer. To avoid the leak, the consumer now waits for all producers to finish before terminating.Support empty
:is()and:where()syntax in CSS (#4232)Previously using these selectors with esbuild would generate a warning. That warning has been removed in this release for these cases.
Improve tree-shaking of
trystatements in dead code (#4224)With this release, esbuild will now remove certain
trystatements if esbuild considers them to be within dead code (i.e. code that is known to not ever be evaluated). For example:// Original code return 'foo' try { return 'bar' } catch {}// Old output (with --minify) return"foo";try{return"bar"}catch{}
// New output (with --minify) return"foo";
Consider negated bigints to have no side effects
While esbuild currently considers
1,-1, and1nto all have no side effects, it didn't previously consider-1nto have no side effects. This is because esbuild does constant folding with numbers but not bigints. However, it meant that unused negative bigint constants were not tree-shaken. With this release, esbuild will now consider these expressions to also be side-effect free:// Original code let a = 1, b = -1, c = 1n, d = -1n// Old output (with --bundle --minify) (()=>{var n=-1n;})();
// New output (with --bundle --minify) (()=>{})();
Support a configurable delay in watch mode before rebuilding (#3476, #4178)
The
watch()API now takes adelayoption that lets you add a delay (in milliseconds) before rebuilding when a change is detected in watch mode. If you use a tool that regenerates multiple source files very slowly, this should make it more likely that esbuild's watch mode won't generate a broken intermediate build before the successful final build. This option is also available via the CLI using the--watch-delay=flag.This should also help avoid confusion about the
watch()API's options argument. It was previously empty to allow for future API expansion, which caused some people to think that the documentation was missing. It's no longer empty now that thewatch()API has an option.Allow mixed array for
entryPointsAPI option (#4223)The TypeScript type definitions now allow you to pass a mixed array of both string literals and object literals to the
entryPointsAPI option, such as['foo.js', { out: 'lib', in: 'bar.js' }]. This was always possible to do in JavaScript but the TypeScript type definitions were previously too restrictive.
... (truncated)
d38c1f0
publish 0.25.6 to npm11e547e
missing ) in release notescc8ac0a
fix trailing comment whitespace1e3fb57
fix #4178:
add the --watch-delay= optionc1f5f18
fix #4209:
disable binary executable optimization on WASM platform (#4210)3ed5ecc
fix incorrect locations in CHANGELOG.md248089c
fix #4224:
allow try statements to become dead42f159c
openharmony: keep makefile targets sorted63256e1
chore: fix some comments (#4211)d803f72
add support for openharmony-arm64 platform (#4212)