Sourced from esbuild's releases.
v0.20.2
Support TypeScript experimental decorators on
abstractclass fields (#3684)With this release, you can now use TypeScript experimental decorators on
abstractclass fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly:// Original code const log = (x: any, y: string) => console.log(y) abstract class Foo { @log abstract foo: string } new class extends Foo { foo = '' }// Old output (with --loader=ts --tsconfig-raw={"compilerOptions":{"experimentalDecorators":true}}) const log = (x, y) => console.log(y); class Foo { } new class extends Foo { foo = ""; }();
// New output (with --loader=ts --tsconfig-raw={"compilerOptions":{"experimentalDecorators":true}}) const log = (x, y) => console.log(y); class Foo { } __decorateClass([ log ], Foo.prototype, "foo", 2); new class extends Foo { foo = ""; }();
JSON loader now preserves
__proto__properties (#3700)Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the
__proto__key. A literal__proto__property in a JavaScript object literal sets the prototype of the object instead of adding a property named__proto__, while a literal__proto__property in a JSON object literal just adds a property named__proto__. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case:// Original code import data from 'data:application/json,{"__proto__":{"fail":true}}' if (Object.getPrototypeOf(data)?.fail) throw 'fail'// Old output (with --bundle) (() => { // <data:application/json,{"proto":{"fail":true}}> var json_proto_fail_true_default = { proto: { fail: true } };
// entry.js if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail) throw "fail"; })();
... (truncated)
Sourced from esbuild's changelog.
0.20.2
Support TypeScript experimental decorators on
abstractclass fields (#3684)With this release, you can now use TypeScript experimental decorators on
abstractclass fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly:// Original code const log = (x: any, y: string) => console.log(y) abstract class Foo { @log abstract foo: string } new class extends Foo { foo = '' }// Old output (with --loader=ts --tsconfig-raw={"compilerOptions":{"experimentalDecorators":true}}) const log = (x, y) => console.log(y); class Foo { } new class extends Foo { foo = ""; }();
// New output (with --loader=ts --tsconfig-raw={"compilerOptions":{"experimentalDecorators":true}}) const log = (x, y) => console.log(y); class Foo { } __decorateClass([ log ], Foo.prototype, "foo", 2); new class extends Foo { foo = ""; }();
JSON loader now preserves
__proto__properties (#3700)Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the
__proto__key. A literal__proto__property in a JavaScript object literal sets the prototype of the object instead of adding a property named__proto__, while a literal__proto__property in a JSON object literal just adds a property named__proto__. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case:// Original code import data from 'data:application/json,{"__proto__":{"fail":true}}' if (Object.getPrototypeOf(data)?.fail) throw 'fail'// Old output (with --bundle) (() => { // <data:application/json,{"proto":{"fail":true}}> var json_proto_fail_true_default = { proto: { fail: true } };
// entry.js if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail) throw "fail"; })();
... (truncated)
617edda
publish 0.20.2 to npm4780075
fix #3700:
json loader preserves __proto__ keys30bed2d
better errors for invalid js decorator syntax300eeb7
ts: allow non-null assertions in js decorators4d997d9
fix #3698:
yarn pnp edge case with tsconfig.jsoncf42954
resolver: improve some debug loggingb0765ae
fix some lintsdfa6206
fix some comments (closes #3683)ae5cc17
fix #3684:
abstract experimental decoratorsc809af0
fix #2388:
allow consuming types without dom types (#3679)4aa56d3
2.4.1e651ce1
chore: Refresh lockfile1775f13
test: Drop unused import to satisfy TS40903db
fix(cst): Do not drop trailing newline after line comment in block-map
if fol...46a816e
fix: Do not skip folding lines after the first in indented block scalars
(fix...750adbe
fix: Stringify flow collection comments in parent (fixes #528)e07998c
ci: Move update action to yaml-playground, where it has write
access5ba73d1
ci: Update yaml-playground build & BrowserStack tests (#524)Sourced from undici's releases.
v6.10.2
What's Changed
- Do not fail test if streams support typed arrays by
@mcollinain nodejs/undici#2978- fix(fetch): properly redirect non-ascii location header url by
@Xvezdain nodejs/undici#2971- perf: Remove double-stringify in setCookie by
@peterverin nodejs/undici#2980- [fix #2982] use DispatcherInterceptor type for Dispatcher#Compose by
@clovis-guillemotin nodejs/undici#2983- fix: make EventSource properties enumerable by
@MattBidewellin nodejs/undici#2987- docs: ✏️ fixed benchmark links by
@benhalversonin nodejs/undici#2991- fix(#2986): bad start check by
@metcoder95in nodejs/undici#2992- fix(H2 Client): bind stream 'data' listener only after received 'response' event by
@St3ffGv4in nodejs/undici#2985- feat: added search input by
@benhalversonin nodejs/undici#2993- chore: validate responses can be consumed without a Content-Length or… by
@jacob-ebeyin nodejs/undici#2995- fix error message by
@KhafraDevin nodejs/undici#2998- Revert "perf: reuse TextDecoder instance (#2863)" by
@panvain nodejs/undici#2999- test: remove only by
@metcoder95in nodejs/undici#3001New Contributors
@Xvezdamade their first contribution in nodejs/undici#2971@petervermade their first contribution in nodejs/undici#2980@clovis-guillemotmade their first contribution in nodejs/undici#2983@MattBidewellmade their first contribution in nodejs/undici#2987@benhalversonmade their first contribution in nodejs/undici#2991@St3ffGv4made their first contribution in nodejs/undici#2985@jacob-ebeymade their first contribution in nodejs/undici#2995Full Changelog: https://github.com/nodejs/undici/compare/v6.10.0...v6.10.2
v6.10.1
Full Changelog: https://github.com/nodejs/undici/compare/v6.10.0...v6.10.1
v6.10.0
What's Changed
- test: fix flakyness of issue-803 test by
@Uzlopakin nodejs/undici#2960- Cleanup format by
@KhafraDevin nodejs/undici#2959- Chore: run tests daily against node nightly by
@mweberxyzin nodejs/undici#2969- fix: fix retry handler option by
@acommodariin nodejs/undici#2962- build(deps): bump node from
4999fa1to577f8ebin /build by@dependabotin nodejs/undici#2974- feat(TS): add types for composed dispatchers by
@metcoder95in nodejs/undici#2967- fix: count for error response and network errors by
@metcoder95in nodejs/undici#2966New Contributors
@mweberxyzmade their first contribution in nodejs/undici#2969@acommodarimade their first contribution in nodejs/undici#2962Full Changelog: https://github.com/nodejs/undici/compare/v6.9.0...v6.10.0
v6.9.0
What's Changed
- feat: add new dispatch compose by
@metcoder95in nodejs/undici#2826- ci: add macos-latest to test-matrix by
@Uzlopakin nodejs/undici#2952
... (truncated)
7485cd9
6.10.2a79d6af
test: remove only (#3001)0ac82a0
Revert "perf: reuse TextDecoder instance (#2863)"
(#2999)bf8c671
fix error message (#2998)ef25209
chore: validate responses can be consumed without a Content-Length or
Transfe...f9cdf56
feat: 🎸 added search input (#2993)c9acca9
fix(H2 Client): bind stream 'data' listener only after received
'response' ev...0ec5a40
fix(#2986):
bad start check (#2992)83f36b7
docs: ✏️ fixed benchmark links (#2991)bc304ff
fix: make EventSource properties enumerable (#2987)