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.19.0 or ~0.19.0. See npm's documentation about semver for more information.
This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.
Work around API deprecations in Deno 1.40.x (#3609, #3611)
Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.
Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.
Reorder implicit file extensions within node_modules (#3341, #3608)
In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.
With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.
Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.
v0.19.12
The "preserve" JSX mode now preserves JSX text verbatim (#3605)
The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).
Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:
// Original code
let el =
<a href={'/'} title=''"'> some text
{foo}
more text </a>
// Old output (with --loader=jsx --jsx=preserve)
let el = <a href="/" title={'"}>
{" some text"}
{foo}
{"more text "}
</a>;
// New output (with --loader=jsx --jsx=preserve)
let el = <a href={"/"} title=''"'> some text
{foo}
more text </a>;
Allow JSX elements as JSX attribute values
JSX has an obscure feature where you can use JSX elements in attribute position without surrounding them with {...}. It looks like this:
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.19.0 or ~0.19.0. See npm's documentation about semver for more information.
This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.
Work around API deprecations in Deno 1.40.x (#3609, #3611)
Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.
Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.
Reorder implicit file extensions within node_modules (#3341, #3608)
In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.
With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.
Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.
0.19.12
The "preserve" JSX mode now preserves JSX text verbatim (#3605)
The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).
Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:
// Original code
let el =
<a href={'/'} title=''"'> some text
{foo}
more text </a>
// Old output (with --loader=jsx --jsx=preserve)
let el = <a href="/" title={'"}>
{" some text"}
{foo}
{"more text "}
</a>;
// New output (with --loader=jsx --jsx=preserve)
let el = <a href={"/"} title=''"'> some text
{foo}
more text </a>;
This is a prerelease version to test our ability to release.
Other than removing or updating dependencies, it contains no intended user-facing changes.
Bumps the dependencies group with 14 updates:
20.10.620.11.171.85.01.86.06.16.06.21.06.16.06.21.02.3.82.3.92.22.02.23.05.0.05.1.00.19.110.20.043.0.043.0.116.6.016.6.210.2.010.3.03.1.13.2.516.2.016.3.03.10.03.11.0Updates
@types/nodefrom 20.10.6 to 20.11.17Commits
Updates
@types/vscodefrom 1.85.0 to 1.86.0Commits
Updates
@typescript-eslint/eslint-pluginfrom 6.16.0 to 6.21.0Release notes
Sourced from
@​typescript-eslint/eslint-plugin's releases.... (truncated)
Changelog
Sourced from
@​typescript-eslint/eslint-plugin's changelog.... (truncated)
Commits
289ee88chore(release): publish 6.21.0f892a72docs(eslint-plugin): mention alternatives in no-explicit-any (#8370)aa5edf7chore(deps): update dependency prettier to v3.2.4 (#8357)1d7447fchore(eslint-plugin): [no-invalid-void-type] fixOptionstyping to reflect ...e2b46e0fix(eslint-plugin): [no-unnecessary-type-assertion] provide valid fixes for a...3bbb78dfeat(eslint-plugin): add rule prefer-find (#8216)9883ee2feat: export plugin metadata (#8331)69bd501fix(eslint-plugin): [class-literal-property-style] allow getter when same key...cd5dff8chore: bump eslint versions (#8338)8d62ee6chore: remove unnecessary eslint-disable comments (#8336)Updates
@typescript-eslint/parserfrom 6.16.0 to 6.21.0Release notes
Sourced from
@​typescript-eslint/parser's releases.... (truncated)
Changelog
Sourced from
@​typescript-eslint/parser's changelog.... (truncated)
Commits
289ee88chore(release): publish 6.21.0aa5edf7chore(deps): update dependency prettier to v3.2.4 (#8357)45c0cb2chore: cleanup test-utils naming/locations (#8341)a01a6e6chore(release): publish 6.20.0a911214chore(release): publish 6.19.17c673a1chore(release): publish 6.19.0aa7ab0echore(release): publish 6.18.11ee3087chore: enable eslint-plugin-jsdoc internally (#8145)21460efchore(release): publish 6.18.0d0977abchore: use nx release (#8194)Updates
@vscode/test-electronfrom 2.3.8 to 2.3.9Changelog
Sourced from
@​vscode/test-electron's changelog.Commits
Updates
@vscode/vscefrom 2.22.0 to 2.23.0Commits
6e959caremove fixture files (#925)f37621dfixes #322 (#924)3fc1a9apublish pre-release on main ci (#923)1be75b2feat: show targets in show command (#922)4df2693show pre-release data in show command (#921)b18c620rewrite video src links (#920)916fd91feat: support --readme-path and --changelog-path (#919)302f02chandle multi line images (#918)160d0e0Filter data from other platforms (#912)3e8410bfeat: Support for yarn workspaces (#493)Updates
chaifrom 5.0.0 to 5.1.0Release notes
Sourced from chai's releases.
Commits
2cf92f5Fix publish script (#1602)1ba37b5Set support in same members (#1583)f224339Assert interface fix (#1601)d504573Implementiterableassertion (#1592)640d932Convert comments in "legal comments" format to jsdoc (#1598)e7f768eCleanup jsdoc comments (#1596)3290eb4Remove useless guards and add parentheses to constuctors (#1593)44b81df5.0.31a4dca15.0.257fef84Fix 1564 (#1566)Updates
esbuildfrom 0.19.11 to 0.20.0Release notes
Sourced from esbuild's releases.
... (truncated)
Changelog
Sourced from esbuild's changelog.
... (truncated)
Commits
2af5ccfpublish 0.20.0 to npm0bccf08fix esbuild/deno-esbuild#5931f87dwork around api deprecations in deno 1.40.x (#3609) (#3611)22a9cf5fix #3341, fix #3608: sort.tsright after.jsf8ec300runnpm pkg fixas suggested by the npm clid7fd1adpublish 0.19.12 to npme04a690fix #3605: print the original JSX AST unmodifiedf571399allow jsx elements as jsx attribute valuesa652e73runmake update-compat-table35c0d65fix #3574: ts type parser bug with infer + extendsUpdates
eslint-config-standard-with-typescriptfrom 43.0.0 to 43.0.1Release notes
Sourced from eslint-config-standard-with-typescript's releases.
Changelog
Sourced from eslint-config-standard-with-typescript's changelog.
Commits
a15c932chore(release): 43.0.1 [skip ci]c7782beMerge pull request #1394 from mightyiam/renovate/semantic-release-23.x5fb79c3chore(deps): update dependency semantic-release to v23d3b4d11Merge pull request #1400 from mightyiam/renovate/node-20.x7414ebachore(deps): update dependency@​types/nodeto v20.11.58470a93Merge pull request #1397 from mightyiam/repo-transfer932ffcedocs: update repository urls372e604Merge pull request #1399 from mightyiam/project8d2f497build: rm add-to-project workflowcd71373Merge pull request #1393 from standard/renovate/node-20.xUpdates
eslint-plugin-nfrom 16.6.0 to 16.6.2Release notes
Sourced from eslint-plugin-n's releases.
Commits
ec5badbRelease 16.6.29ddd351chore: update tests to use eslintrc options5fc2198fix: no-callback-literal ignore unknown nodes (#163)c191101chore: add non-rule-change issue template (#159)ad8f4f4chore: move rule tests parserOptions to ruleTester (#157)bc6c538Release 16.6.12419888fix: eslint 7.0 support (#156)Updates
mochafrom 10.2.0 to 10.3.0Release notes
Sourced from mocha's releases.
... (truncated)
Changelog
Sourced from mocha's changelog.
Superseded by #244.