Sourced from ava's releases.
v6.1.3
What's Changed
- Include Node.js 22 in supported engines and test matrix by
@lenovouserin avajs/ava#3328- Add VS Code debugging instructions for Yarn PnP projects by
@bitjsonin avajs/ava#3317- Document
serialconfiguration option by@turadgin avajs/ava#3321New Contributors
@bitjsonmade their first contribution in avajs/ava#3317@turadgmade their first contribution in avajs/ava#3321@lenovousermade their first contribution in avajs/ava#3328Full Changelog: https://github.com/avajs/ava/compare/v6.1.2...v6.1.3
f8bf00c
6.1.3002b3a0
Include Node.js 22 in supported engines and test matrixec1a8d2
Document serial configuration option01ec280
Add VS Code debugging instructions for Yarn PnP projectsSourced from esbuild's releases.
v0.21.4
Update support for import assertions and import attributes in node (#3778)
Import assertions (the
assertkeyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with--target=node22or above:▲ [WARNING] The "assert" keyword is not supported in the configured target environment ("node22") [assert-to-with]example.mjs:1:40: 1 │ import json from "esbuild/package.json" assert { type: "json" } │ ~~~~~~ ╵ withDid you mean to use "with" instead of "assert"?
Import attributes (the
withkeyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with--target=node18.NifNis 20 or greater.Fix
for awaittransform when a label is presentThis release fixes a bug where the
for awaittransform, which wraps the loop in atrystatement, previously failed to also move the loop's label into thetrystatement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code:// Original code async function test() { outer: for await (const x of [Promise.resolve([0, 1])]) { for (const y of x) if (y) break outer throw 'fail' } }// Old output (with --target=es6) function test() { return __async(this, null, function* () { outer: try { for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) { const x = temp.value; for (const y of x) if (y) break outer; throw "fail"; } } catch (temp) { error = [temp]; } finally { try { more && (temp = iter.return) && (yield temp.call(iter)); } finally { if (error) throw error[0]; } }
... (truncated)
Sourced from esbuild's changelog.
0.21.4
Update support for import assertions and import attributes in node (#3778)
Import assertions (the
assertkeyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with--target=node22or above:▲ [WARNING] The "assert" keyword is not supported in the configured target environment ("node22") [assert-to-with]example.mjs:1:40: 1 │ import json from "esbuild/package.json" assert { type: "json" } │ ~~~~~~ ╵ withDid you mean to use "with" instead of "assert"?
Import attributes (the
withkeyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with--target=node18.NifNis 20 or greater.Fix
for awaittransform when a label is presentThis release fixes a bug where the
for awaittransform, which wraps the loop in atrystatement, previously failed to also move the loop's label into thetrystatement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code:// Original code async function test() { outer: for await (const x of [Promise.resolve([0, 1])]) { for (const y of x) if (y) break outer throw 'fail' } }// Old output (with --target=es6) function test() { return __async(this, null, function* () { outer: try { for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) { const x = temp.value; for (const y of x) if (y) break outer; throw "fail"; } } catch (temp) { error = [temp]; } finally { try { more && (temp = iter.return) && (yield temp.call(iter)); } finally { if (error) throw error[0]; }
... (truncated)
67cbf87
publish 0.21.4 to npm4ad11c3
fix #3639,
fix #3646:
pass with to onResolve516ca31
fix #3343:
allow bundle-internal string aliases9e2f304
fix #3416,
fix #3425:
better enum constant folding8f1faf7
implement late constant-folding for && || ??7d50a50
implement late constant-folding of string enums1b29ac7
fold equality checks after cross-module inliningd7a8bf3
formatting support for @position-try (for #3773)5069410
fix #3778:
import assertions/attributes for node11d568c
run make update-compat-tableSourced from execa's releases.
v9.1.0
Features (types)
- Export
TemplateExpressiontype. (#1049)v9.0.2
Bug fixes (types)
- Do not require using
--lib domfor TypeScript users (#1043, #1044)- Fix type of the
rejectoption (#1046)v9.0.1
Bug fixes (types)
- Fix types not being importable (#1033) 3bdab60
- Fix complexity bug with types (#1037) 6cc519b
- Fix complexity bug with types (#1035) fee011d
v9.0.0
This major release brings many important features including:
- Split the output into lines, or progressively iterate over them.
- Transform or filter the input/output using simple functions.
- Print the output to the terminal while still retrieving it programmatically.
- Redirect the input/output from/to a file.
- Advanced piping between multiple subprocesses.
- Improved verbose mode, for debugging.
- More detailed errors, including when terminating subprocesses.
- Enhanced template string syntax.
- Global/shared options.
- Web streams and Transform streams support.
- Convert the subprocess to a stream.
- New documentation with many examples.
Please check the release post for a high-level overview! For the full list of breaking changes, features and bug fixes, please read below.
Thanks
@younggglcy,@koshic,@am0o0and@codesmith-emmyfor your help!
One of the maintainers
@ehmickyis looking for a remote full-time position. Specialized in Node.js back-ends and CLIs, he led Netlify Build, Plugins and Configuration for 2.5 years. Feel free to contact him on his website or on LinkedIn!
Breaking changes (not types)
Dropped support for Node.js version
<18.19.0and20.0.0 - 20.4.0. (834e3726)When the
encodingoption is'buffer', the output (result.stdout,result.stderr,result.all) is now anUint8Arrayinstead of aBuffer. For more information, see this blog post. (by@younggglcy) (#586)</tr></table>
... (truncated)
62d02af
9.1.0733d6ff
Split CI jobs (#1052)3b11ac8
Check types on TypeScript 5.1 + latest (#1051)de8e7da
Document minimum TypeScript version (#1050)2d84752
Export TemplateExpression type (#1049)b8c131c
9.0.2e2903e9
Run TypeScript on the types (#1042)ab2a9ed
Fix type of result when using the reject: false option (#1046)11bbd9d
Fix type of TransformStream (#1044)6f4941e
Fix typing of web streams (#1043)