Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore(deps-dev): Bump esbuild from 0.19.0 to 0.19.1 (#6886)
Bumps [esbuild](https://github.com/evanw/esbuild) from 0.19.0 to 0.19.1. <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.19.1</h2> <ul> <li> <p>Fix a regression with <code>baseURL</code> in <code>tsconfig.json</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/3307">#3307</a>)</p> <p>The previous release moved <code>tsconfig.json</code> path resolution before <code>--packages=external</code> checks to allow the <a href="https://www.typescriptlang.org/tsconfig#paths"><code>paths</code> field</a> in <code>tsconfig.json</code> to avoid a package being marked as external. However, that reordering accidentally broke the behavior of the <code>baseURL</code> field from <code>tsconfig.json</code>. This release moves these path resolution rules around again in an attempt to allow both of these cases to work.</p> </li> <li> <p>Parse TypeScript type arguments for JavaScript decorators (<a href="https://redirect.github.com/evanw/esbuild/issues/3308">#3308</a>)</p> <p>When parsing JavaScript decorators in TypeScript (i.e. with <code>experimentalDecorators</code> disabled), esbuild previously didn't parse type arguments. Type arguments will now be parsed starting with this release. For example:</p> <pre lang="ts"><code>@foo<number> @bar<number, string>() class Foo {} </code></pre> </li> <li> <p>Fix glob patterns matching extra stuff at the end (<a href="https://redirect.github.com/evanw/esbuild/issues/3306">#3306</a>)</p> <p>Previously glob patterns such as <code>./*.js</code> would incorrectly behave like <code>./*.js*</code> during path matching (also matching <code>.js.map</code> files, for example). This was never intentional behavior, and has now been fixed.</p> </li> <li> <p>Change the permissions of esbuild's generated output files (<a href="https://redirect.github.com/evanw/esbuild/issues/3285">#3285</a>)</p> <p>This release changes the permissions of the output files that esbuild generates to align with the default behavior of node's <a href="https://nodejs.org/api/fs.html#fswritefilesyncfile-data-options"><code>fs.writeFileSync</code></a> function. Since most tools written in JavaScript use <code>fs.writeFileSync</code>, this should make esbuild more consistent with how other JavaScript build tools behave.</p> <p>The full Unix-y details: Unix permissions use three-digit octal notation where the three digits mean "user, group, other" in that order. Within a digit, 4 means "read" and 2 means "write" and 1 means "execute". So 6 == 4 + 2 == read + write. Previously esbuild uses 0644 permissions (the leading 0 means octal notation) but the permissions for <code>fs.writeFileSync</code> defaults to 0666, so esbuild will now use 0666 permissions. This does not necessarily mean that the files esbuild generates will end up having 0666 permissions, however, as there is another Unix feature called "umask" where the operating system masks out some of these bits. If your umask is set to 0022 then the generated files will have 0644 permissions, and if your umask is set to 0002 then the generated files will have 0664 permissions.</p> </li> <li> <p>Fix a subtle CSS ordering issue with <code>@import</code> and <code>@layer</code></p> <p>With this release, esbuild may now introduce additional <code>@layer</code> rules when bundling CSS to better preserve the layer ordering of the input code. Here's an example of an edge case where this matters:</p> <pre lang="css"><code>/* entry.css */ @import "a.css"; @import "b.css"; @import "a.css"; </code></pre> <pre lang="css"><code>/* a.css */ @layer a { body { background: red; } } </code></pre> <pre lang="css"><code>/* b.css */ @layer b { body { background: green; </code></pre> </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.19.1</h2> <ul> <li> <p>Fix a regression with <code>baseURL</code> in <code>tsconfig.json</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/3307">#3307</a>)</p> <p>The previous release moved <code>tsconfig.json</code> path resolution before <code>--packages=external</code> checks to allow the <a href="https://www.typescriptlang.org/tsconfig#paths"><code>paths</code> field</a> in <code>tsconfig.json</code> to avoid a package being marked as external. However, that reordering accidentally broke the behavior of the <code>baseURL</code> field from <code>tsconfig.json</code>. This release moves these path resolution rules around again in an attempt to allow both of these cases to work.</p> </li> <li> <p>Parse TypeScript type arguments for JavaScript decorators (<a href="https://redirect.github.com/evanw/esbuild/issues/3308">#3308</a>)</p> <p>When parsing JavaScript decorators in TypeScript (i.e. with <code>experimentalDecorators</code> disabled), esbuild previously didn't parse type arguments. Type arguments will now be parsed starting with this release. For example:</p> <pre lang="ts"><code>@foo<number> @bar<number, string>() class Foo {} </code></pre> </li> <li> <p>Fix glob patterns matching extra stuff at the end (<a href="https://redirect.github.com/evanw/esbuild/issues/3306">#3306</a>)</p> <p>Previously glob patterns such as <code>./*.js</code> would incorrectly behave like <code>./*.js*</code> during path matching (also matching <code>.js.map</code> files, for example). This was never intentional behavior, and has now been fixed.</p> </li> <li> <p>Change the permissions of esbuild's generated output files (<a href="https://redirect.github.com/evanw/esbuild/issues/3285">#3285</a>)</p> <p>This release changes the permissions of the output files that esbuild generates to align with the default behavior of node's <a href="https://nodejs.org/api/fs.html#fswritefilesyncfile-data-options"><code>fs.writeFileSync</code></a> function. Since most tools written in JavaScript use <code>fs.writeFileSync</code>, this should make esbuild more consistent with how other JavaScript build tools behave.</p> <p>The full Unix-y details: Unix permissions use three-digit octal notation where the three digits mean "user, group, other" in that order. Within a digit, 4 means "read" and 2 means "write" and 1 means "execute". So 6 == 4 + 2 == read + write. Previously esbuild uses 0644 permissions (the leading 0 means octal notation) but the permissions for <code>fs.writeFileSync</code> defaults to 0666, so esbuild will now use 0666 permissions. This does not necessarily mean that the files esbuild generates will end up having 0666 permissions, however, as there is another Unix feature called "umask" where the operating system masks out some of these bits. If your umask is set to 0022 then the generated files will have 0644 permissions, and if your umask is set to 0002 then the generated files will have 0664 permissions.</p> </li> <li> <p>Fix a subtle CSS ordering issue with <code>@import</code> and <code>@layer</code></p> <p>With this release, esbuild may now introduce additional <code>@layer</code> rules when bundling CSS to better preserve the layer ordering of the input code. Here's an example of an edge case where this matters:</p> <pre lang="css"><code>/* entry.css */ @import "a.css"; @import "b.css"; @import "a.css"; </code></pre> <pre lang="css"><code>/* a.css */ @layer a { body { background: red; } } </code></pre> <pre lang="css"><code>/* b.css */ @layer b { body { </code></pre> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/evanw/esbuild/commit/49801f761347d53bd1f6a88767bb79e257f9fbb9"><code>49801f7</code></a> publish 0.19.1 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/1fca4aa243ab4d0c042abb091c6262de9755dbcf"><code>1fca4aa</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/3307">#3307</a>: regression with tsconfig <code>baseURL</code></li> <li><a href="https://github.com/evanw/esbuild/commit/a973f87ec0e60b4452c24584d2b18fd5e101d198"><code>a973f87</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/3308">#3308</a>: TS type arguments for JS decorators</li> <li><a href="https://github.com/evanw/esbuild/commit/be9e0981cd97e508c857c2be6f8510df0335347a"><code>be9e098</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/3306">#3306</a>: handle lack of a trailing glob wildcard</li> <li><a href="https://github.com/evanw/esbuild/commit/83917cfaa56dde1e15c3a904d33de5a3f8ad066c"><code>83917cf</code></a> css: handle external <code>@import</code> condition chains</li> <li><a href="https://github.com/evanw/esbuild/commit/d81d759c9e4ac15f2cb7afec449b26fede3c06af"><code>d81d759</code></a> adjust source range for duplicate case warning</li> <li><a href="https://github.com/evanw/esbuild/commit/4b67d82cca14c4d3146d4acf7c603b907831b3d9"><code>4b67d82</code></a> tsconfig: options outside compilerOptions (<a href="https://redirect.github.com/evanw/esbuild/issues/3301">#3301</a>)</li> <li><a href="https://github.com/evanw/esbuild/commit/813fb3aba7c8510e6f61e64edc934129ad31dacd"><code>813fb3a</code></a> api: reduce console output when an error is thrown</li> <li><a href="https://github.com/evanw/esbuild/commit/ab9007c3a45b029050eb54e8647aed10e5db1d07"><code>ab9007c</code></a> fix(TsconfigRaw): <code>baseUrl</code> to be string (<a href="https://redirect.github.com/evanw/esbuild/issues/3299">#3299</a>)</li> <li><a href="https://github.com/evanw/esbuild/commit/4202ea03587c67cb51af5e33c41d7fb9061f0d48"><code>4202ea0</code></a> css: fix ordering with <code>@import</code> and <code>@layer</code></li> <li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.19.0...v0.19.1">compare view</a></li> </ul> </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Loading branch information
1 parent
161c867
commit 7646fe1