-
Notifications
You must be signed in to change notification settings - Fork 85
Commit 1f18aab
authored
build(deps-dev): bump the development-dependencies group with 5 updates (#101)
Bumps the development-dependencies group with 5 updates:
| Package | From | To |
| --- | --- | --- |
| [ava](https://github.com/avajs/ava) | `6.0.1` | `6.1.1` |
| [c8](https://github.com/bcoe/c8) | `8.0.1` | `9.1.0` |
| [dotenv](https://github.com/motdotla/dotenv) | `16.3.1` | `16.4.1` |
| [esbuild](https://github.com/evanw/esbuild) | `0.19.11` | `0.20.0` |
| [undici](https://github.com/nodejs/undici) | `6.2.1` | `6.6.0` |
Updates `ava` from 6.0.1 to 6.1.1
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/avajs/ava/releases">ava's
releases</a>.</em></p>
<blockquote>
<h2>v6.1.1</h2>
<h2>What's Changed</h2>
<ul>
<li>Fix 'previous failures' in watch mode always incrementing by <a
href="https://github.com/novemberborn"><code>@novemberborn</code></a>
in <a
href="https://redirect.github.com/avajs/ava/pull/3297">avajs/ava#3297</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/avajs/ava/compare/v6.1.0...v6.1.1">https://github.com/avajs/ava/compare/v6.1.0...v6.1.1</a></p>
<h2>v6.1.0</h2>
<h2>What's Changed</h2>
<ul>
<li>
<p>Implement <code>registerCompletionHandler()</code> by <a
href="https://github.com/novemberborn"><code>@novemberborn</code></a>
in <a
href="https://redirect.github.com/avajs/ava/pull/3283">avajs/ava#3283</a></p>
<p>AVA 6 expects test code to clean up gracefully when the tests are
complete, allowing the test environment (worker thread or child process)
to exit. If this does not happen, AVA will report a timeout. You can use
<code>registerCompletionHandler()</code> to perform any other clean up
(or indeed exit the process) after AVA has completed the test execution.
See <a
href="https://github.com/avajs/ava/blob/main/docs/08-common-pitfalls.md#timeouts-because-a-file-failed-to-exit">the
description here</a>.</p>
</li>
<li>
<p>Fix potential bug with watch mode when no failed test files are
written by <a
href="https://github.com/novemberborn"><code>@novemberborn</code></a>
in <a
href="https://redirect.github.com/avajs/ava/pull/3287">avajs/ava#3287</a></p>
</li>
<li>
<p>Fix <code>ava/internal</code> ESM type module by <a
href="https://github.com/codetheweb"><code>@codetheweb</code></a> in <a
href="https://redirect.github.com/avajs/ava/pull/3292">avajs/ava#3292</a></p>
</li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/avajs/ava/compare/v6.0.1...v6.1.0">https://github.com/avajs/ava/compare/v6.0.1...v6.1.0</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/avajs/ava/commit/2e0c2b1cef779e1c092eb60f0a9558bb9cf4c848"><code>2e0c2b1</code></a>
6.1.1</li>
<li><a
href="https://github.com/avajs/ava/commit/5161bf77d4cd5ae2fcfd8882177e7d4a4660a9f8"><code>5161bf7</code></a>
Update dependencies</li>
<li><a
href="https://github.com/avajs/ava/commit/15dddf3ff5407b6941cf320bcb60720ac4d24a9c"><code>15dddf3</code></a>
Fix external-assertions snapshot for Node.js 20.11</li>
<li><a
href="https://github.com/avajs/ava/commit/db0fdb2925cb71b6981316b08d843cc74ff10f4a"><code>db0fdb2</code></a>
Fix 'previous failures' in watch mode always incrementing</li>
<li><a
href="https://github.com/avajs/ava/commit/735bf4172a1618d3f843eb97a68bf454aac6a329"><code>735bf41</code></a>
Update TypeScript recipe to suggest --import flag and tsimp</li>
<li><a
href="https://github.com/avajs/ava/commit/aae39b20ba3ef80e5bedb1e5882432a3cd7c44eb"><code>aae39b2</code></a>
6.1.0</li>
<li><a
href="https://github.com/avajs/ava/commit/c3e2c72e0a99738cf4720027243de98ce5bb2d69"><code>c3e2c72</code></a>
Fix ava/internal ESM type module</li>
<li><a
href="https://github.com/avajs/ava/commit/0a050243ea13df959e6c1536b2513b5fe3557690"><code>0a05024</code></a>
Implement registerCompletionHandler()</li>
<li><a
href="https://github.com/avajs/ava/commit/cc8b8397247a843a178cf732274823b13787c1f6"><code>cc8b839</code></a>
Ensure AVA exits with code 1 after an unexpected process.exit() in a
test worker</li>
<li><a
href="https://github.com/avajs/ava/commit/35f6c86bcddcd251910775f13c52aded6bbed4e5"><code>35f6c86</code></a>
Fix potential bug with watch mode when no failed test files are
written</li>
<li>Additional commits viewable in <a
href="https://github.com/avajs/ava/compare/v6.0.1...v6.1.1">compare
view</a></li>
</ul>
</details>
<br />
Updates `c8` from 8.0.1 to 9.1.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/bcoe/c8/releases">c8's
releases</a>.</em></p>
<blockquote>
<h2>v9.1.0</h2>
<h2><a
href="https://github.com/bcoe/c8/compare/v9.0.0...v9.1.0">9.1.0</a>
(2024-01-11)</h2>
<h3>Features</h3>
<ul>
<li>support passing reporter options from config (<a
href="https://redirect.github.com/bcoe/c8/issues/459">#459</a>) (<a
href="https://github.com/bcoe/c8/commit/88db5db56ece1686b02af7ce3b5480653069b975">88db5db</a>)</li>
</ul>
<h3>Bug Fixes</h3>
<ul>
<li><strong>refactor:</strong> remove stale check for
createDynamicModule (<a
href="https://github.com/bcoe/c8/commit/5e18365b1507682a3d7873b17ebeb6f963b251cb">5e18365</a>)</li>
</ul>
<h2>v9.0.0</h2>
<h2><a
href="https://github.com/bcoe/c8/compare/v8.0.1...v9.0.0">9.0.0</a>
(2024-01-03)</h2>
<h3>⚠ BREAKING CHANGES</h3>
<ul>
<li><strong>build:</strong> minimum Node.js version is now 14.14.0</li>
</ul>
<h3>Features</h3>
<ul>
<li><strong>build:</strong> minimum Node.js version is now 14.14.0 (<a
href="https://github.com/bcoe/c8/commit/2cdc86bd0ac67ecf0f700212dc5f8a830ff9164f">2cdc86b</a>)</li>
<li><strong>deps:</strong> update foreground-child to promise API (<a
href="https://redirect.github.com/bcoe/c8/issues/512">#512</a>) (<a
href="https://github.com/bcoe/c8/commit/b46b6401274488db5b1027a78090257095ae4f72">b46b640</a>)</li>
<li><strong>deps:</strong> use Node.js built in rm (<a
href="https://github.com/bcoe/c8/commit/2cdc86bd0ac67ecf0f700212dc5f8a830ff9164f">2cdc86b</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/bcoe/c8/blob/main/CHANGELOG.md">c8's
changelog</a>.</em></p>
<blockquote>
<h2><a
href="https://github.com/bcoe/c8/compare/v9.0.0...v9.1.0">9.1.0</a>
(2024-01-11)</h2>
<h3>Features</h3>
<ul>
<li>support passing reporter options from config (<a
href="https://redirect.github.com/bcoe/c8/issues/459">#459</a>) (<a
href="https://github.com/bcoe/c8/commit/88db5db56ece1686b02af7ce3b5480653069b975">88db5db</a>)</li>
</ul>
<h3>Bug Fixes</h3>
<ul>
<li><strong>refactor:</strong> remove stale check for
createDynamicModule (<a
href="https://github.com/bcoe/c8/commit/5e18365b1507682a3d7873b17ebeb6f963b251cb">5e18365</a>)</li>
</ul>
<h2><a
href="https://github.com/bcoe/c8/compare/v8.0.1...v9.0.0">9.0.0</a>
(2024-01-03)</h2>
<h3>⚠ BREAKING CHANGES</h3>
<ul>
<li><strong>build:</strong> minimum Node.js version is now 14.14.0</li>
</ul>
<h3>Features</h3>
<ul>
<li><strong>build:</strong> minimum Node.js version is now 14.14.0 (<a
href="https://github.com/bcoe/c8/commit/2cdc86bd0ac67ecf0f700212dc5f8a830ff9164f">2cdc86b</a>)</li>
<li><strong>deps:</strong> update foreground-child to promise API (<a
href="https://redirect.github.com/bcoe/c8/issues/512">#512</a>) (<a
href="https://github.com/bcoe/c8/commit/b46b6401274488db5b1027a78090257095ae4f72">b46b640</a>)</li>
<li><strong>deps:</strong> use Node.js built in rm (<a
href="https://github.com/bcoe/c8/commit/2cdc86bd0ac67ecf0f700212dc5f8a830ff9164f">2cdc86b</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/bcoe/c8/commit/4ae2a4d7dea2fd861e46aa786d46f391265f21fb"><code>4ae2a4d</code></a>
chore(main): release 9.1.0 (<a
href="https://redirect.github.com/bcoe/c8/issues/513">#513</a>)</li>
<li><a
href="https://github.com/bcoe/c8/commit/88db5db56ece1686b02af7ce3b5480653069b975"><code>88db5db</code></a>
feat: support passing reporter options from config (<a
href="https://redirect.github.com/bcoe/c8/issues/459">#459</a>)</li>
<li><a
href="https://github.com/bcoe/c8/commit/5e18365b1507682a3d7873b17ebeb6f963b251cb"><code>5e18365</code></a>
fix(refactor): remove stale check for createDynamicModule</li>
<li><a
href="https://github.com/bcoe/c8/commit/128bee23366cb35106f5e163e99ca2ab33dafba6"><code>128bee2</code></a>
chore(main): release 9.0.0 (<a
href="https://redirect.github.com/bcoe/c8/issues/510">#510</a>)</li>
<li><a
href="https://github.com/bcoe/c8/commit/8724c706ef7a21877e6dad1185f09dce11ddd0d2"><code>8724c70</code></a>
chore(deps): update dependency <code>@types/node</code> to v20 (<a
href="https://redirect.github.com/bcoe/c8/issues/496">#496</a>)</li>
<li><a
href="https://github.com/bcoe/c8/commit/66705b59557ba1e48b63172e99ef4ceb34ac1711"><code>66705b5</code></a>
chore(deps): update dependency typescript to v5 (<a
href="https://redirect.github.com/bcoe/c8/issues/458">#458</a>)</li>
<li><a
href="https://github.com/bcoe/c8/commit/b46b6401274488db5b1027a78090257095ae4f72"><code>b46b640</code></a>
feat(deps): update foreground-child to promise API (<a
href="https://redirect.github.com/bcoe/c8/issues/512">#512</a>)</li>
<li><a
href="https://github.com/bcoe/c8/commit/ef672da08d8e078bf49ea73631fb46eabf8a5dae"><code>ef672da</code></a>
test: fix snapshot (<a
href="https://redirect.github.com/bcoe/c8/issues/511">#511</a>)</li>
<li><a
href="https://github.com/bcoe/c8/commit/2cdc86bd0ac67ecf0f700212dc5f8a830ff9164f"><code>2cdc86b</code></a>
chore(deps): Remove rimraf (<a
href="https://redirect.github.com/bcoe/c8/issues/509">#509</a>)</li>
<li>See full diff in <a
href="https://github.com/bcoe/c8/compare/v8.0.1...v9.1.0">compare
view</a></li>
</ul>
</details>
<br />
Updates `dotenv` from 16.3.1 to 16.4.1
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/motdotla/dotenv/blob/master/CHANGELOG.md">dotenv's
changelog</a>.</em></p>
<blockquote>
<h2><a
href="https://github.com/motdotla/dotenv/compare/v16.4.0...v16.4.1">16.4.1</a>
(2024-01-24)</h2>
<ul>
<li>Patch support for array as <code>path</code> option <a
href="https://redirect.github.com/motdotla/dotenv/pull/797">#797</a></li>
</ul>
<h2><a
href="https://github.com/motdotla/dotenv/compare/v16.3.2...v16.4.0">16.4.0</a>
(2024-01-23)</h2>
<ul>
<li>Add <code>error.code</code> to error messages around
<code>.env.vault</code> decryption handling <a
href="https://redirect.github.com/motdotla/dotenv/pull/795">#795</a></li>
<li>Add ability to find <code>.env.vault</code> file when filename(s)
passed as an array <a
href="https://redirect.github.com/motdotla/dotenv/pull/784">#784</a></li>
</ul>
<h2><a
href="https://github.com/motdotla/dotenv/compare/v16.3.1...v16.3.2">16.3.2</a>
(2024-01-18)</h2>
<h3>Added</h3>
<ul>
<li>Add debug message when no encoding set <a
href="https://redirect.github.com/motdotla/dotenv/pull/735">#735</a></li>
</ul>
<h3>Changed</h3>
<ul>
<li>Fix output typing for <code>populate</code> <a
href="https://redirect.github.com/motdotla/dotenv/pull/792">#792</a></li>
<li>Use subarray instead of slice <a
href="https://redirect.github.com/motdotla/dotenv/pull/793">#793</a></li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/motdotla/dotenv/commit/e251ee244a77fc8f6100d0efaae87ca561f5e33a"><code>e251ee2</code></a>
16.4.1</li>
<li><a
href="https://github.com/motdotla/dotenv/commit/a7fee29bd0392fc8da039e809f833e6df0b6fd3c"><code>a7fee29</code></a>
update CHANGELOG 🪵</li>
<li><a
href="https://github.com/motdotla/dotenv/commit/579d136c2175eaac14a284e58e531e3c2d169b8c"><code>579d136</code></a>
update README</li>
<li><a
href="https://github.com/motdotla/dotenv/commit/7ea2f81a2efc97fee568bb0470a9786638f84b27"><code>7ea2f81</code></a>
Merge pull request <a
href="https://redirect.github.com/motdotla/dotenv/issues/798">#798</a>
from motdotla/fix-tests</li>
<li><a
href="https://github.com/motdotla/dotenv/commit/6b829d2551c6b90d1d7d67d46471d845083b1fff"><code>6b829d2</code></a>
demonstrate currently failing (pending) test. multiple env files should
merge</li>
<li><a
href="https://github.com/motdotla/dotenv/commit/3e2284b89d31648d89c63f696de9c7e6d5438518"><code>3e2284b</code></a>
largely remove mocking from tests except where useful</li>
<li><a
href="https://github.com/motdotla/dotenv/commit/2039c4edc6cc0b29409004e447feca61abf424ac"><code>2039c4e</code></a>
wip: fix tests</li>
<li><a
href="https://github.com/motdotla/dotenv/commit/48a6ade3bf4f1e00f61b74607ee3bc58f7b7064d"><code>48a6ade</code></a>
Merge pull request <a
href="https://redirect.github.com/motdotla/dotenv/issues/797">#797</a>
from tran-simon/master</li>
<li><a
href="https://github.com/motdotla/dotenv/commit/cfd735d7d00f01e3772a35b541b1b141fd5a5c5c"><code>cfd735d</code></a>
fix: support array for path option</li>
<li><a
href="https://github.com/motdotla/dotenv/commit/a44cb3dd00abdd77f3268be111cf9dd68e9a8e91"><code>a44cb3d</code></a>
update README</li>
<li>Additional commits viewable in <a
href="https://github.com/motdotla/dotenv/compare/v16.3.1...v16.4.1">compare
view</a></li>
</ul>
</details>
<br />
Updates `esbuild` from 0.19.11 to 0.20.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/evanw/esbuild/releases">esbuild's
releases</a>.</em></p>
<blockquote>
<h2>v0.20.0</h2>
<p><strong>This release deliberately contains backwards-incompatible
changes.</strong> To avoid automatically picking up releases like this,
you should either be pinning the exact version of <code>esbuild</code>
in your <code>package.json</code> file (recommended) or be using a
version range syntax that only accepts patch upgrades such as
<code>^0.19.0</code> or <code>~0.19.0</code>. See npm's documentation
about <a
href="https://docs.npmjs.com/cli/v6/using-npm/semver/">semver</a> for
more information.</p>
<p>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.</p>
<ul>
<li>
<p>Work around API deprecations in Deno 1.40.x (<a
href="https://redirect.github.com/evanw/esbuild/issues/3609">#3609</a>,
<a
href="https://redirect.github.com/evanw/esbuild/pull/3611">#3611</a>)</p>
<p><a href="https://deno.com/blog/v1.40">Deno 1.40.0</a> 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.</p>
<p>Unfortunately, doing this introduces a breaking change. The newer
child process APIs lack a way to synchronously terminate esbuild's child
process, so calling <code>esbuild.stop()</code> 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
<code>stop()</code> function has been changed to return a promise, and
you now have to change <code>esbuild.stop()</code> to <code>await
esbuild.stop()</code> in all of your Deno tests.</p>
</li>
<li>
<p>Reorder implicit file extensions within <code>node_modules</code> (<a
href="https://redirect.github.com/evanw/esbuild/issues/3341">#3341</a>,
<a
href="https://redirect.github.com/evanw/esbuild/issues/3608">#3608</a>)</p>
<p>In <a
href="https://github.com/evanw/esbuild/releases/v0.18.0">version
0.18.0</a>, esbuild changed the behavior of implicit file extensions
within <code>node_modules</code> directories (i.e. in published
packages) to prefer <code>.js</code> over <code>.ts</code> even when the
<code>--resolve-extensions=</code> order prefers <code>.ts</code> over
<code>.js</code> (which it does by default). However, doing that also
accidentally made esbuild prefer <code>.css</code> over
<code>.ts</code>, which caused problems for people that published
packages containing both TypeScript and CSS in files with the same
name.</p>
<p>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
<code>.tsx,.ts,.jsx,.js,.css,.json</code> which used to become
<code>.jsx,.js,.css,.json,.tsx,.ts</code> in <code>node_modules</code>
directories. With this release it will now become
<code>.jsx,.js,.tsx,.ts,.css,.json</code> instead.</p>
<p>Why even rewrite the implicit file extension order at all? One reason
is because the <code>.js</code> file is more likely to behave correctly
than the <code>.ts</code> file. The behavior of the <code>.ts</code>
file may depend on <code>tsconfig.json</code> and the
<code>tsconfig.json</code> file may not even be published, or may use
<code>extends</code> to refer to a base <code>tsconfig.json</code> file
that wasn't published. People can get into this situation when they
forget to add all <code>.ts</code> files to their
<code>.npmignore</code> file before publishing to npm. Picking
<code>.js</code> over <code>.ts</code> helps make it more likely that
resulting bundle will behave correctly.</p>
</li>
</ul>
<h2>v0.19.12</h2>
<ul>
<li>
<p>The "preserve" JSX mode now preserves JSX text verbatim (<a
href="https://redirect.github.com/evanw/esbuild/issues/3605">#3605</a>)</p>
<p>The <a href="https://facebook.github.io/jsx/">JSX specification</a>
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 <a
href="https://twitter.com/jarredsumner/status/1456118847937781764">they
are different</a> (esbuild <a
href="https://twitter.com/evanwallace/status/1456122279453208576">deliberately
follows TypeScript</a> by the way).</p>
<p>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:</p>
<pre lang="jsx"><code>// Original code
let el =
<a href={'/'} title='&apos;&quot;'> some text
{foo}
more text </a>
<p>// Old output (with --loader=jsx --jsx=preserve)
let el = <a href="/" title={<code>'&quot;</code>}>
{" some text"}
{foo}
{"more text "}
</a>;</p>
<p>// New output (with --loader=jsx --jsx=preserve)
let el = <a href={"/"} title='&apos;&quot;'>
some text
{foo}
more text </a>;
</code></pre></p>
</li>
<li>
<p>Allow JSX elements as JSX attribute values</p>
<p>JSX has an obscure feature where you can use JSX elements in
attribute position without surrounding them with <code>{...}</code>. It
looks like this:</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/evanw/esbuild/blob/main/CHANGELOG.md">esbuild's
changelog</a>.</em></p>
<blockquote>
<h2>0.20.0</h2>
<p><strong>This release deliberately contains backwards-incompatible
changes.</strong> To avoid automatically picking up releases like this,
you should either be pinning the exact version of <code>esbuild</code>
in your <code>package.json</code> file (recommended) or be using a
version range syntax that only accepts patch upgrades such as
<code>^0.19.0</code> or <code>~0.19.0</code>. See npm's documentation
about <a
href="https://docs.npmjs.com/cli/v6/using-npm/semver/">semver</a> for
more information.</p>
<p>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.</p>
<ul>
<li>
<p>Work around API deprecations in Deno 1.40.x (<a
href="https://redirect.github.com/evanw/esbuild/issues/3609">#3609</a>,
<a
href="https://redirect.github.com/evanw/esbuild/pull/3611">#3611</a>)</p>
<p><a href="https://deno.com/blog/v1.40">Deno 1.40.0</a> 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.</p>
<p>Unfortunately, doing this introduces a breaking change. The newer
child process APIs lack a way to synchronously terminate esbuild's child
process, so calling <code>esbuild.stop()</code> 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
<code>stop()</code> function has been changed to return a promise, and
you now have to change <code>esbuild.stop()</code> to <code>await
esbuild.stop()</code> in all of your Deno tests.</p>
</li>
<li>
<p>Reorder implicit file extensions within <code>node_modules</code> (<a
href="https://redirect.github.com/evanw/esbuild/issues/3341">#3341</a>,
<a
href="https://redirect.github.com/evanw/esbuild/issues/3608">#3608</a>)</p>
<p>In <a
href="https://github.com/evanw/esbuild/releases/v0.18.0">version
0.18.0</a>, esbuild changed the behavior of implicit file extensions
within <code>node_modules</code> directories (i.e. in published
packages) to prefer <code>.js</code> over <code>.ts</code> even when the
<code>--resolve-extensions=</code> order prefers <code>.ts</code> over
<code>.js</code> (which it does by default). However, doing that also
accidentally made esbuild prefer <code>.css</code> over
<code>.ts</code>, which caused problems for people that published
packages containing both TypeScript and CSS in files with the same
name.</p>
<p>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
<code>.tsx,.ts,.jsx,.js,.css,.json</code> which used to become
<code>.jsx,.js,.css,.json,.tsx,.ts</code> in <code>node_modules</code>
directories. With this release it will now become
<code>.jsx,.js,.tsx,.ts,.css,.json</code> instead.</p>
<p>Why even rewrite the implicit file extension order at all? One reason
is because the <code>.js</code> file is more likely to behave correctly
than the <code>.ts</code> file. The behavior of the <code>.ts</code>
file may depend on <code>tsconfig.json</code> and the
<code>tsconfig.json</code> file may not even be published, or may use
<code>extends</code> to refer to a base <code>tsconfig.json</code> file
that wasn't published. People can get into this situation when they
forget to add all <code>.ts</code> files to their
<code>.npmignore</code> file before publishing to npm. Picking
<code>.js</code> over <code>.ts</code> helps make it more likely that
resulting bundle will behave correctly.</p>
</li>
</ul>
<h2>0.19.12</h2>
<ul>
<li>
<p>The "preserve" JSX mode now preserves JSX text verbatim (<a
href="https://redirect.github.com/evanw/esbuild/issues/3605">#3605</a>)</p>
<p>The <a href="https://facebook.github.io/jsx/">JSX specification</a>
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 <a
href="https://twitter.com/jarredsumner/status/1456118847937781764">they
are different</a> (esbuild <a
href="https://twitter.com/evanwallace/status/1456122279453208576">deliberately
follows TypeScript</a> by the way).</p>
<p>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:</p>
<pre lang="jsx"><code>// Original code
let el =
<a href={'/'} title='&apos;&quot;'> some text
{foo}
more text </a>
<p>// Old output (with --loader=jsx --jsx=preserve)
let el = <a href="/" title={<code>'&quot;</code>}>
{" some text"}
{foo}
{"more text "}
</a>;</p>
<p>// New output (with --loader=jsx --jsx=preserve)
let el = <a href={"/"} title='&apos;&quot;'>
some text
{foo}
more text </a>;
</code></pre></p>
</li>
<li>
<p>Allow JSX elements as JSX attribute values</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/evanw/esbuild/commit/2af5ccf478812d2d7226ad4435d46fbbb3419a8c"><code>2af5ccf</code></a>
publish 0.20.0 to npm</li>
<li><a
href="https://github.com/evanw/esbuild/commit/0bccf08675867c8ce6662b1ab4aae21973083d99"><code>0bccf08</code></a>
fix <a
href="https://redirect.github.com/esbuild/deno-esbuild/pull/5">esbuild/deno-esbuild#5</a></li>
<li><a
href="https://github.com/evanw/esbuild/commit/931f87db267cf86f63d940c0a77072ef45e96128"><code>931f87d</code></a>
work around api deprecations in deno 1.40.x (<a
href="https://redirect.github.com/evanw/esbuild/issues/3609">#3609</a>)
(<a
href="https://redirect.github.com/evanw/esbuild/issues/3611">#3611</a>)</li>
<li><a
href="https://github.com/evanw/esbuild/commit/22a9cf5754d402aabfe75aeda0266c3a970b0ee1"><code>22a9cf5</code></a>
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/3341">#3341</a>,
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/3608">#3608</a>:
sort <code>.ts</code> right after <code>.js</code></li>
<li><a
href="https://github.com/evanw/esbuild/commit/f8ec3007b68c5bfb755317e5c7051f63184c514b"><code>f8ec300</code></a>
run <code>npm pkg fix</code> as suggested by the npm cli</li>
<li><a
href="https://github.com/evanw/esbuild/commit/d7fd1ad35715cda76eb33343b7c07b275e402a2e"><code>d7fd1ad</code></a>
publish 0.19.12 to npm</li>
<li><a
href="https://github.com/evanw/esbuild/commit/e04a6900b7659146aef670e62a0d16c6f75cfd70"><code>e04a690</code></a>
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/3605">#3605</a>:
print the original JSX AST unmodified</li>
<li><a
href="https://github.com/evanw/esbuild/commit/f5713992227188d137c485d27b6956c6de814b9a"><code>f571399</code></a>
allow jsx elements as jsx attribute values</li>
<li><a
href="https://github.com/evanw/esbuild/commit/a652e730ff07b9081470ef6965f3d54daa7b2aab"><code>a652e73</code></a>
run <code>make update-compat-table</code></li>
<li><a
href="https://github.com/evanw/esbuild/commit/35c0d65b9d4f29a26176404d2890d1b499634e9f"><code>35c0d65</code></a>
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/3574">#3574</a>:
ts type parser bug with infer + extends</li>
<li>Additional commits viewable in <a
href="https://github.com/evanw/esbuild/compare/v0.19.11...v0.20.0">compare
view</a></li>
</ul>
</details>
<br />
Updates `undici` from 6.2.1 to 6.6.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/nodejs/undici/releases">undici's
releases</a>.</em></p>
<blockquote>
<h2>v6.6.0</h2>
<h2>What's Changed</h2>
<ul>
<li>add webSocket example by <a
href="https://github.com/mertcanaltin"><code>@mertcanaltin</code></a>
in <a
href="https://redirect.github.com/nodejs/undici/pull/2626">nodejs/undici#2626</a></li>
<li>chore: remove atomic-sleep as dev dependency by <a
href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2648">nodejs/undici#2648</a></li>
<li>chore: remove semver as dev dependency by <a
href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2646">nodejs/undici#2646</a></li>
<li>chore: remove table as dev dependency by <a
href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2649">nodejs/undici#2649</a></li>
<li>chore: remove delay as dev dependency by <a
href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2647">nodejs/undici#2647</a></li>
<li>chore: reduce noise in test-logs test/issue-2349.js by <a
href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2655">nodejs/undici#2655</a></li>
<li>chore: fix faketimer warning in test/request-timeout.js by <a
href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2656">nodejs/undici#2656</a></li>
<li>chore: reduce noise in test logs test/client-node-max-header-size.js
by <a href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2654">nodejs/undici#2654</a></li>
<li>refactor: use fromInnerResponse by <a
href="https://github.com/tsctx"><code>@tsctx</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2635">nodejs/undici#2635</a></li>
<li>fix: support deflate raw responses by <a
href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2650">nodejs/undici#2650</a></li>
<li>Support building for externally shared js builtins by <a
href="https://github.com/mochaaP"><code>@mochaaP</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2643">nodejs/undici#2643</a></li>
<li>fix: typo clampAndCoarsenConnectionTimingInfo by <a
href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2653">nodejs/undici#2653</a></li>
<li>chore: use 'node:'-prefix for requiring node core modules by <a
href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2662">nodejs/undici#2662</a></li>
<li>build(deps-dev): bump husky from 8.0.3 to 9.0.7 by <a
href="https://github.com/dependabot"><code>@dependabot</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2667">nodejs/undici#2667</a></li>
<li>build(deps-dev): bump cronometro from 1.2.0 to 2.0.2 by <a
href="https://github.com/dependabot"><code>@dependabot</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2668">nodejs/undici#2668</a></li>
<li>remove timers/promises import by <a
href="https://github.com/KhafraDev"><code>@KhafraDev</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2665">nodejs/undici#2665</a></li>
<li>chore: fix various codesmells by <a
href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2669">nodejs/undici#2669</a></li>
<li>chore: remove this alias in agent.js by <a
href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2671">nodejs/undici#2671</a></li>
<li>chore: use optional chaining by <a
href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2666">nodejs/undici#2666</a></li>
<li>chore: small perf improvements by <a
href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2661">nodejs/undici#2661</a></li>
<li>implement spec changes from a while ago by <a
href="https://github.com/KhafraDev"><code>@KhafraDev</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2676">nodejs/undici#2676</a></li>
<li>websocket: fix close when no closing code is received by <a
href="https://github.com/KhafraDev"><code>@KhafraDev</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2680">nodejs/undici#2680</a></li>
<li>fix: make ci less flaky by <a
href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2684">nodejs/undici#2684</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/mochaaP"><code>@mochaaP</code></a> made
their first contribution in <a
href="https://redirect.github.com/nodejs/undici/pull/2643">nodejs/undici#2643</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/nodejs/undici/compare/v6.5.0...v6.6.0">https://github.com/nodejs/undici/compare/v6.5.0...v6.6.0</a></p>
<h2>v6.5.0</h2>
<h2>What's Changed</h2>
<ul>
<li>build(deps-dev): bump jsdom from 23.2.0 to 24.0.0 by <a
href="https://github.com/dependabot"><code>@dependabot</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2632">nodejs/undici#2632</a></li>
<li>feat: Implement EventSource by <a
href="https://github.com/Uzlopak"><code>@Uzlopak</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2608">nodejs/undici#2608</a></li>
<li>fix: readable body by <a
href="https://github.com/ronag"><code>@ronag</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2642">nodejs/undici#2642</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/nodejs/undici/compare/v6.4.0...v6.5.0">https://github.com/nodejs/undici/compare/v6.4.0...v6.5.0</a></p>
<h2>v6.4.0</h2>
<h2>What's Changed</h2>
<ul>
<li>refactor: version cleanup by <a
href="https://github.com/tsctx"><code>@tsctx</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2605">nodejs/undici#2605</a></li>
<li>cacheStorage: separate matchAll logic by <a
href="https://github.com/KhafraDev"><code>@KhafraDev</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2599">nodejs/undici#2599</a></li>
<li>cleanup index by <a
href="https://github.com/KhafraDev"><code>@KhafraDev</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2598">nodejs/undici#2598</a></li>
<li>feat: port <code>balanced-pool</code>, <code>ca-fingerprint</code>,
<code>client-abort</code> tests to <code>node:test</code> by <a
href="https://github.com/sosukesuzuki"><code>@sosukesuzuki</code></a>
in <a
href="https://redirect.github.com/nodejs/undici/pull/2584">nodejs/undici#2584</a></li>
<li>ci: unpin nodejs workflow version by <a
href="https://github.com/dominykas"><code>@dominykas</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2434">nodejs/undici#2434</a></li>
<li>test(<a
href="https://redirect.github.com/nodejs/undici/issues/2600">#2600</a>):
Flaky debug test by <a
href="https://github.com/metcoder95"><code>@metcoder95</code></a> in <a
href="https://redirect.github.com/nodejs/undici/pull/2607">nodejs/undici#2607</a></li>
<li>fix: h2 hang issue with empty body by <a
href="https://github.com/timursevimli"><code>@timursevimli</code></a>
in <a
href="https://redirect.github.com/nodejs/undici/pull/2601">nodejs/undici#2601</a></li>
<li>Fix tests for Node.js v21 by <a
href="https://github.com/sosukesuzuki"><code>@sosukesuzuki</code></a>
in <a
href="https://redirect.github.com/nodejs/undici/pull/2609">nodejs/undici#2609</a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/nodejs/undici/commit/fa2d2d29a46412f8fb1f1a1ecf07b73e0db66a32"><code>fa2d2d2</code></a>
Bumped v6.6.0</li>
<li><a
href="https://github.com/nodejs/undici/commit/9bcf6f867fa82ef10d8b23ecb1cc3bf1f95e4041"><code>9bcf6f8</code></a>
fix: make ci less flaky (<a
href="https://redirect.github.com/nodejs/undici/issues/2684">#2684</a>)</li>
<li><a
href="https://github.com/nodejs/undici/commit/0808a721570baaa10e6386a9e50bd34278814afe"><code>0808a72</code></a>
websocket: fix close when no closing code is received (<a
href="https://redirect.github.com/nodejs/undici/issues/2680">#2680</a>)</li>
<li><a
href="https://github.com/nodejs/undici/commit/8220e7d192449f7d7417a414931849ef6573bc65"><code>8220e7d</code></a>
implement spec changes from a while ago (<a
href="https://redirect.github.com/nodejs/undici/issues/2676">#2676</a>)</li>
<li><a
href="https://github.com/nodejs/undici/commit/f1d7ada7eb2292932065a7c9ab23569b8a6e1720"><code>f1d7ada</code></a>
chore: small perf improvements (<a
href="https://redirect.github.com/nodejs/undici/issues/2661">#2661</a>)</li>
<li><a
href="https://github.com/nodejs/undici/commit/3e37392bd425ad7f49d99f649f9783294951ffa1"><code>3e37392</code></a>
chore: use optional chaining (<a
href="https://redirect.github.com/nodejs/undici/issues/2666">#2666</a>)</li>
<li><a
href="https://github.com/nodejs/undici/commit/ee35bb0b7a92944d3572062de4e96680b6fdeb61"><code>ee35bb0</code></a>
chore: remove this alias in agent.js (<a
href="https://redirect.github.com/nodejs/undici/issues/2671">#2671</a>)</li>
<li><a
href="https://github.com/nodejs/undici/commit/82477d734df73bcfb507af9394fa165d316c1eb3"><code>82477d7</code></a>
chore: fix various codesmells (<a
href="https://redirect.github.com/nodejs/undici/issues/2669">#2669</a>)</li>
<li><a
href="https://github.com/nodejs/undici/commit/2144da490ebcdc02d2b065d0b720137e12a049bb"><code>2144da4</code></a>
remove timers/promises import (<a
href="https://redirect.github.com/nodejs/undici/issues/2665">#2665</a>)</li>
<li><a
href="https://github.com/nodejs/undici/commit/bed84897c34769c620ed43df657b2015bf221dfe"><code>bed8489</code></a>
build(deps-dev): bump cronometro from 1.2.0 to 2.0.2 (<a
href="https://redirect.github.com/nodejs/undici/issues/2668">#2668</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/nodejs/undici/compare/v6.2.1...v6.6.0">compare
view</a></li>
</ul>
</details>
<br />
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions
</details>
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>1 parent 86576b3 commit 1f18aabCopy full SHA for 1f18aab
2 files changed
+166
-160
lines changed
0 commit comments