Bump esbuild from 0.15.5 to 0.16.14 #338

Closed

dependabot[bot] wants to merge 1 commit from dependabot/npm_and_yarn/esbuild-0.16.14 into master

dependabot[bot] commented

2023-01-05 11:03:41 +01:00

(Migrated from github.com)

Bumps esbuild from 0.15.5 to 0.16.14.

Release notes

Sourced from esbuild's releases.

v0.16.14
Preserve some comments in expressions (#2721)

Various tools give semantic meaning to comments embedded inside of expressions. For example, Webpack and Vite have special "magic comments" that can be used to affect code splitting behavior:
import(/* webpackChunkName: "foo" */ '../foo');
import(/* @vite-ignore */ dynamicVar);
new Worker(/* webpackChunkName: "bar" */ new URL("../bar.ts", import.meta.url));
new Worker(new URL('./path', import.meta.url), /* @vite-ignore */ dynamicOptions);
Since esbuild can be used as a preprocessor for these tools (e.g. to strip TypeScript types), it can be problematic if esbuild doesn't do additional work to try to retain these comments. Previously esbuild special-cased Webpack comments in these specific locations in the AST. But Vite would now like to use similar comments, and likely other tools as well.

So with this release, esbuild now will attempt to preserve some comments inside of expressions in more situations than before. This behavior is mainly intended to preserve these special "magic comments" that are meant for other tools to consume, although esbuild will no longer only preserve Webpack-specific comments so it should now be tool-agnostic. There is no guarantee that all such comments will be preserved (especially when --minify-syntax is enabled). So this change does not mean that esbuild is now usable as a code formatter. In particular comment preservation is more likely to happen with leading comments than with trailing comments. You should put comments that you want to be preserved before the relevant expression instead of after it. Also note that this change does not retain any more statement-level comments than before (i.e. comments not embedded inside of expressions). Comment preservation is not enabled when --minify-whitespace is enabled (which is automatically enabled when you use --minify).
v0.16.13

Publish a new bundle visualization tool

While esbuild provides bundle metadata via the --metafile flag, previously esbuild left analysis of it completely up to third-party tools (well, outside of the rudimentary --analyze flag). However, the esbuild website now has a built-in bundle visualization tool:

https://esbuild.github.io/analyze/

You can pass --metafile to esbuild to output bundle metadata, then upload that JSON file to this tool to visualize your bundle. This is helpful for answering questions such as:

Which packages are included in my bundle?

How did a specific file get included?

How small did a specific file compress to?

Was a specific file tree-shaken or not?

I'm publishing this tool because I think esbuild should provide some answer to "how do I visualize my bundle" without requiring people to reach for third-party tools. At the moment the tool offers two types of visualizations: a radial "sunburst chart" and a linear "flame chart". They serve slightly different but overlapping use cases (e.g. the sunburst chart is more keyboard-accessible while the flame chart is easier with the mouse). This tool may continue to evolve over time.

Fix --metafile and --mangle-cache with --watch (#1357)

The CLI calls the Go API and then also writes out the metafile and/or mangle cache JSON files if those features are enabled. This extra step is necessary because these files are returned by the Go API as in-memory strings. However, this extra step accidentally didn't happen for all builds after the initial build when watch mode was enabled. This behavior used to work but it was broken in version 0.14.18 by the introduction of the mangle cache feature. This release fixes the combination of these features, so the metafile and mangle cache features should now work with watch mode. This behavior was only broken for the CLI, not for the JS or Go APIs.

Add an original field to the metafile

The metadata file JSON now has an additional field: each import in an input file now contains the pre-resolved path in the original field in addition to the post-resolved path in the path field. This means it's now possible to run certain additional analysis over your bundle. For example, you should be able to use this to detect when the same package subpath is represented multiple times in the bundle, either because multiple versions of a package were bundled or because a package is experiencing the dual-package hazard.

v0.16.12
Loader defaults to js for extensionless files (#2776)

Certain packages contain files without an extension. For example, the yargs package contains the file yargs/yargs which has no extension. Node, Webpack, and Parcel can all understand code that imports yargs/yargs because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for "" (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this:
CLI:
esbuild --bundle --loader:=css

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.16.14
Preserve some comments in expressions (#2721)

Various tools give semantic meaning to comments embedded inside of expressions. For example, Webpack and Vite have special "magic comments" that can be used to affect code splitting behavior:
import(/* webpackChunkName: "foo" */ '../foo');
import(/* @vite-ignore */ dynamicVar);
new Worker(/* webpackChunkName: "bar" */ new URL("../bar.ts", import.meta.url));
new Worker(new URL('./path', import.meta.url), /* @vite-ignore */ dynamicOptions);
Since esbuild can be used as a preprocessor for these tools (e.g. to strip TypeScript types), it can be problematic if esbuild doesn't do additional work to try to retain these comments. Previously esbuild special-cased Webpack comments in these specific locations in the AST. But Vite would now like to use similar comments, and likely other tools as well.

So with this release, esbuild now will attempt to preserve some comments inside of expressions in more situations than before. This behavior is mainly intended to preserve these special "magic comments" that are meant for other tools to consume, although esbuild will no longer only preserve Webpack-specific comments so it should now be tool-agnostic. There is no guarantee that all such comments will be preserved (especially when --minify-syntax is enabled). So this change does not mean that esbuild is now usable as a code formatter. In particular comment preservation is more likely to happen with leading comments than with trailing comments. You should put comments that you want to be preserved before the relevant expression instead of after it. Also note that this change does not retain any more statement-level comments than before (i.e. comments not embedded inside of expressions). Comment preservation is not enabled when --minify-whitespace is enabled (which is automatically enabled when you use --minify).
0.16.13

Publish a new bundle visualization tool

While esbuild provides bundle metadata via the --metafile flag, previously esbuild left analysis of it completely up to third-party tools (well, outside of the rudimentary --analyze flag). However, the esbuild website now has a built-in bundle visualization tool:

https://esbuild.github.io/analyze/

You can pass --metafile to esbuild to output bundle metadata, then upload that JSON file to this tool to visualize your bundle. This is helpful for answering questions such as:

Which packages are included in my bundle?

How did a specific file get included?

How small did a specific file compress to?

Was a specific file tree-shaken or not?

I'm publishing this tool because I think esbuild should provide some answer to "how do I visualize my bundle" without requiring people to reach for third-party tools. At the moment the tool offers two types of visualizations: a radial "sunburst chart" and a linear "flame chart". They serve slightly different but overlapping use cases (e.g. the sunburst chart is more keyboard-accessible while the flame chart is easier with the mouse). This tool may continue to evolve over time.

Fix --metafile and --mangle-cache with --watch (#1357)

The CLI calls the Go API and then also writes out the metafile and/or mangle cache JSON files if those features are enabled. This extra step is necessary because these files are returned by the Go API as in-memory strings. However, this extra step accidentally didn't happen for all builds after the initial build when watch mode was enabled. This behavior used to work but it was broken in version 0.14.18 by the introduction of the mangle cache feature. This release fixes the combination of these features, so the metafile and mangle cache features should now work with watch mode. This behavior was only broken for the CLI, not for the JS or Go APIs.

Add an original field to the metafile

The metadata file JSON now has an additional field: each import in an input file now contains the pre-resolved path in the original field in addition to the post-resolved path in the path field. This means it's now possible to run certain additional analysis over your bundle. For example, you should be able to use this to detect when the same package subpath is represented multiple times in the bundle, either because multiple versions of a package were bundled or because a package is experiencing the dual-package hazard.

0.16.12

Loader defaults to js for extensionless files (#2776)

Certain packages contain files without an extension. For example, the yargs package contains the file yargs/yargs which has no extension. Node, Webpack, and Parcel can all understand code that imports yargs/yargs because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for "" (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this:

CLI:

... (truncated)

Commits

93328af publish 0.16.14 to npm
98bd7c3 preserve comments in import assertions too
f8311c4 fix #2721: make comment-preservation more general
c169006 change LegalCommentsBeforeToken into ranges
56f4ef9 parser recovery for ?? with || and/or &&
85fd2b1 more error text for #2790
930f60d link to analyzer in help text
0db0b46 publish 0.16.13 to npm
eda632d mention the bundle analyzer in the release notes
9234378 add the original field to the metafile
Additional commits viewable in compare view

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 commands and options

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 ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [esbuild](https://github.com/evanw/esbuild) from 0.15.5 to 0.16.14. <details> <summary>Release notes</summary> Sourced from <a href="https://github.com/evanw/esbuild/releases">esbuild's releases</a>. <blockquote> <h2>v0.16.14</h2> <ul> <li> Preserve some comments in expressions (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2721">#2721</a>) Various tools give semantic meaning to comments embedded inside of expressions. For example, Webpack and Vite have special "magic comments" that can be used to affect code splitting behavior: <pre lang="js"><code>import(/* webpackChunkName: "foo" */ '../foo'); import(/* @vite-ignore */ dynamicVar); new Worker(/* webpackChunkName: "bar" */ new URL("../bar.ts", import.meta.url)); new Worker(new URL('./path', import.meta.url), /* @vite-ignore */ dynamicOptions); </code></pre> Since esbuild can be used as a preprocessor for these tools (e.g. to strip TypeScript types), it can be problematic if esbuild doesn't do additional work to try to retain these comments. Previously esbuild special-cased Webpack comments in these specific locations in the AST. But Vite would now like to use similar comments, and likely other tools as well. So with this release, esbuild now will attempt to preserve some comments inside of expressions in more situations than before. This behavior is mainly intended to preserve these special "magic comments" that are meant for other tools to consume, although esbuild will no longer only preserve Webpack-specific comments so it should now be tool-agnostic. There is no guarantee that all such comments will be preserved (especially when <code>--minify-syntax</code> is enabled). So this change does not mean that esbuild is now usable as a code formatter. In particular comment preservation is more likely to happen with leading comments than with trailing comments. You should put comments that you want to be preserved before the relevant expression instead of after it. Also note that this change does not retain any more statement-level comments than before (i.e. comments not embedded inside of expressions). Comment preservation is not enabled when <code>--minify-whitespace</code> is enabled (which is automatically enabled when you use <code>--minify</code>). </li> </ul> <h2>v0.16.13</h2> <ul> <li> Publish a new bundle visualization tool While esbuild provides bundle metadata via the <code>--metafile</code> flag, previously esbuild left analysis of it completely up to third-party tools (well, outside of the rudimentary <code>--analyze</code> flag). However, the esbuild website now has a built-in bundle visualization tool: <ul> <li><a href="https://esbuild.github.io/analyze/">https://esbuild.github.io/analyze/</a></li> </ul> You can pass <code>--metafile</code> to esbuild to output bundle metadata, then upload that JSON file to this tool to visualize your bundle. This is helpful for answering questions such as: <ul> <li>Which packages are included in my bundle?</li> <li>How did a specific file get included?</li> <li>How small did a specific file compress to?</li> <li>Was a specific file tree-shaken or not?</li> </ul> I'm publishing this tool because I think esbuild should provide some answer to "how do I visualize my bundle" without requiring people to reach for third-party tools. At the moment the tool offers two types of visualizations: a radial "sunburst chart" and a linear "flame chart". They serve slightly different but overlapping use cases (e.g. the sunburst chart is more keyboard-accessible while the flame chart is easier with the mouse). This tool may continue to evolve over time. </li> <li> Fix <code>--metafile</code> and <code>--mangle-cache</code> with <code>--watch</code> (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/1357">#1357</a>) The CLI calls the Go API and then also writes out the metafile and/or mangle cache JSON files if those features are enabled. This extra step is necessary because these files are returned by the Go API as in-memory strings. However, this extra step accidentally didn't happen for all builds after the initial build when watch mode was enabled. This behavior used to work but it was broken in version 0.14.18 by the introduction of the mangle cache feature. This release fixes the combination of these features, so the metafile and mangle cache features should now work with watch mode. This behavior was only broken for the CLI, not for the JS or Go APIs. </li> <li> Add an <code>original</code> field to the metafile The metadata file JSON now has an additional field: each import in an input file now contains the pre-resolved path in the <code>original</code> field in addition to the post-resolved path in the <code>path</code> field. This means it's now possible to run certain additional analysis over your bundle. For example, you should be able to use this to detect when the same package subpath is represented multiple times in the bundle, either because multiple versions of a package were bundled or because a package is experiencing the <a href="https://nodejs.org/api/packages.html#dual-package-hazard">dual-package hazard</a>. </li> </ul> <h2>v0.16.12</h2> <ul> <li> Loader defaults to <code>js</code> for extensionless files (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2776">#2776</a>) Certain packages contain files without an extension. For example, the <code>yargs</code> package contains the file <code>yargs/yargs</code> which has no extension. Node, Webpack, and Parcel can all understand code that imports <code>yargs/yargs</code> because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for <code>""</code> (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this: <ul> <li> CLI: <pre><code>esbuild --bundle --loader:=css </code></pre> </li> </ul> </li> </ul>  </blockquote> ... (truncated) </details> <details> <summary>Changelog</summary> Sourced from <a href="https://github.com/evanw/esbuild/blob/main/CHANGELOG.md">esbuild's changelog</a>. <blockquote> <h2>0.16.14</h2> <ul> <li> Preserve some comments in expressions (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2721">#2721</a>) Various tools give semantic meaning to comments embedded inside of expressions. For example, Webpack and Vite have special "magic comments" that can be used to affect code splitting behavior: <pre lang="js"><code>import(/* webpackChunkName: "foo" */ '../foo'); import(/* @vite-ignore */ dynamicVar); new Worker(/* webpackChunkName: "bar" */ new URL("../bar.ts", import.meta.url)); new Worker(new URL('./path', import.meta.url), /* @vite-ignore */ dynamicOptions); </code></pre> Since esbuild can be used as a preprocessor for these tools (e.g. to strip TypeScript types), it can be problematic if esbuild doesn't do additional work to try to retain these comments. Previously esbuild special-cased Webpack comments in these specific locations in the AST. But Vite would now like to use similar comments, and likely other tools as well. So with this release, esbuild now will attempt to preserve some comments inside of expressions in more situations than before. This behavior is mainly intended to preserve these special "magic comments" that are meant for other tools to consume, although esbuild will no longer only preserve Webpack-specific comments so it should now be tool-agnostic. There is no guarantee that all such comments will be preserved (especially when <code>--minify-syntax</code> is enabled). So this change does not mean that esbuild is now usable as a code formatter. In particular comment preservation is more likely to happen with leading comments than with trailing comments. You should put comments that you want to be preserved before the relevant expression instead of after it. Also note that this change does not retain any more statement-level comments than before (i.e. comments not embedded inside of expressions). Comment preservation is not enabled when <code>--minify-whitespace</code> is enabled (which is automatically enabled when you use <code>--minify</code>). </li> </ul> <h2>0.16.13</h2> <ul> <li> Publish a new bundle visualization tool While esbuild provides bundle metadata via the <code>--metafile</code> flag, previously esbuild left analysis of it completely up to third-party tools (well, outside of the rudimentary <code>--analyze</code> flag). However, the esbuild website now has a built-in bundle visualization tool: <ul> <li><a href="https://esbuild.github.io/analyze/">https://esbuild.github.io/analyze/</a></li> </ul> You can pass <code>--metafile</code> to esbuild to output bundle metadata, then upload that JSON file to this tool to visualize your bundle. This is helpful for answering questions such as: <ul> <li>Which packages are included in my bundle?</li> <li>How did a specific file get included?</li> <li>How small did a specific file compress to?</li> <li>Was a specific file tree-shaken or not?</li> </ul> I'm publishing this tool because I think esbuild should provide some answer to "how do I visualize my bundle" without requiring people to reach for third-party tools. At the moment the tool offers two types of visualizations: a radial "sunburst chart" and a linear "flame chart". They serve slightly different but overlapping use cases (e.g. the sunburst chart is more keyboard-accessible while the flame chart is easier with the mouse). This tool may continue to evolve over time. </li> <li> Fix <code>--metafile</code> and <code>--mangle-cache</code> with <code>--watch</code> (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/1357">#1357</a>) The CLI calls the Go API and then also writes out the metafile and/or mangle cache JSON files if those features are enabled. This extra step is necessary because these files are returned by the Go API as in-memory strings. However, this extra step accidentally didn't happen for all builds after the initial build when watch mode was enabled. This behavior used to work but it was broken in version 0.14.18 by the introduction of the mangle cache feature. This release fixes the combination of these features, so the metafile and mangle cache features should now work with watch mode. This behavior was only broken for the CLI, not for the JS or Go APIs. </li> <li> Add an <code>original</code> field to the metafile The metadata file JSON now has an additional field: each import in an input file now contains the pre-resolved path in the <code>original</code> field in addition to the post-resolved path in the <code>path</code> field. This means it's now possible to run certain additional analysis over your bundle. For example, you should be able to use this to detect when the same package subpath is represented multiple times in the bundle, either because multiple versions of a package were bundled or because a package is experiencing the <a href="https://nodejs.org/api/packages.html#dual-package-hazard">dual-package hazard</a>. </li> </ul> <h2>0.16.12</h2> <ul> <li> Loader defaults to <code>js</code> for extensionless files (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2776">#2776</a>) Certain packages contain files without an extension. For example, the <code>yargs</code> package contains the file <code>yargs/yargs</code> which has no extension. Node, Webpack, and Parcel can all understand code that imports <code>yargs/yargs</code> because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for <code>""</code> (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this: <ul> <li>CLI:</li> </ul> </li> </ul>  </blockquote> ... (truncated) </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/evanw/esbuild/commit/93328af7dcf842f750c3e782bd83997e4f817e8d"><code>93328af</code></a> publish 0.16.14 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/98bd7c37018c08f26a08c4a00c25315b971ed8b7"><code>98bd7c3</code></a> preserve comments in import assertions too</li> <li><a href="https://github.com/evanw/esbuild/commit/f8311c452672d7d6fee56681b5a3fb72a353c54a"><code>f8311c4</code></a> fix <a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2721">#2721</a>: make comment-preservation more general</li> <li><a href="https://github.com/evanw/esbuild/commit/c16900674402e3130f53a04a9cde5c21f3e7e1ee"><code>c169006</code></a> change <code>LegalCommentsBeforeToken</code> into ranges</li> <li><a href="https://github.com/evanw/esbuild/commit/56f4ef9b1a51a60ea2c6efc6ada98784771ecce6"><code>56f4ef9</code></a> parser recovery for <code>??</code> with <code>||</code> and/or <code>&&</code></li> <li><a href="https://github.com/evanw/esbuild/commit/85fd2b185eaff3b9cd47a5dbcb49c8e661586de7"><code>85fd2b1</code></a> more error text for <a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2790">#2790</a></li> <li><a href="https://github.com/evanw/esbuild/commit/930f60d694d377d739f9ccb8c7053a16e88aafe3"><code>930f60d</code></a> link to analyzer in help text</li> <li><a href="https://github.com/evanw/esbuild/commit/0db0b46399de81fb29f6fcb65dfb5fad3638b6d8"><code>0db0b46</code></a> publish 0.16.13 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/eda632d4b58f78c502aaa5d10611e7c8597670d8"><code>eda632d</code></a> mention the bundle analyzer in the release notes</li> <li><a href="https://github.com/evanw/esbuild/commit/92343786415fe8e8e5ad145fd24e8955fab2c142"><code>9234378</code></a> add the <code>original</code> field to the metafile</li> <li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.15.5...v0.16.14">compare view</a></li> </ul> </details> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=esbuild&package-manager=npm_and_yarn&previous-version=0.15.5&new-version=0.16.14)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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> 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 ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>

dependabot[bot] commented

2023-01-05 11:18:19 +01:00

(Migrated from github.com)

Looks like esbuild is up-to-date now, so this is no longer needed.

Commenting is not possible because the repository is archived.

No reviewers