build(deps): bump esbuild from 0.12.25 to 0.12.26

[dependabot]

Bumps esbuild from 0.12.25 to 0.12.26.

Release notes

Sourced from esbuild's releases.

v0.12.26

• Add --analyze to print information about the bundle (#1568)

  The --metafile= flag tells esbuild to write information about the bundle into the provided metadata file in JSON format. It contains information about the input files and which other files each one imports, as well as the output files and which input files they include. This information is sufficient to answer many questions such as:

  • Which files are in my bundle?
  • What's are the biggest files in my bundle?
  • Why is this file included in my bundle?

  Previously you had to either write your own code to answer these questions, or use another tool such as https://bundle-buddy.com/esbuild to visualize the data. Starting with this release you can now also use --analyze to enable esbuild's built-in visualizer. It looks like this:

  $ esbuild --bundle example.jsx --outfile=out.js --minify --analyze
  out.js  27.6kb
  ⚡ Done in 6ms
  out.js                                                                    27.6kb  100.0%
  ├ node_modules/react-dom/cjs/react-dom-server.browser.production.min.js  19.2kb   69.8%
  ├ node_modules/react/cjs/react.production.min.js                          5.9kb   21.4%
  ├ node_modules/object-assign/index.js                                     965b     3.4%
  ├ example.jsx                                                             137b     0.5%
  ├ node_modules/react-dom/server.browser.js                                 50b     0.2%
  └ node_modules/react/index.js                                              50b     0.2%
  

  This tells you what input files were bundled into each output file as well as the final minified size contribution of each input file as well as the percentage of the output file it takes up. You can also enable verbose analysis with --analyze=verbose to see why each input file was included (i.e. which files imported it from the entry point file):

  $ esbuild --bundle example.jsx --outfile=out.js --minify --analyze=verbose
  out.js  27.6kb
  ⚡ Done in 6ms
  out.js ─────────────────────────────────────────────────────────────────── 27.6kb ─ 100.0%
  ├ node_modules/react-dom/cjs/react-dom-server.browser.production.min.js ─ 19.2kb ── 69.8%
  │  └ node_modules/react-dom/server.browser.js
  │     └ example.jsx
  ├ node_modules/react/cjs/react.production.min.js ───────────────────────── 5.9kb ── 21.4%
  │  └ node_modules/react/index.js
  │     └ example.jsx
  ├ node_modules/object-assign/index.js ──────────────────────────────────── 965b ──── 3.4%
  │  └ node_modules/react-dom/cjs/react-dom-server.browser.production.min.js
  │     └ node_modules/react-dom/server.browser.js
  │        └ example.jsx
  ├ example.jsx ──────────────────────────────────────────────────────────── 137b ──── 0.5%
  ├ node_modules/react-dom/server.browser.js ──────────────────────────────── 50b ──── 0.2%
  │  └ example.jsx
  

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.12.26

• Add --analyze to print information about the bundle (#1568)

  The --metafile= flag tells esbuild to write information about the bundle into the provided metadata file in JSON format. It contains information about the input files and which other files each one imports, as well as the output files and which input files they include. This information is sufficient to answer many questions such as:

  • Which files are in my bundle?
  • What's are the biggest files in my bundle?
  • Why is this file included in my bundle?

  Previously you had to either write your own code to answer these questions, or use another tool such as https://bundle-buddy.com/esbuild to visualize the data. Starting with this release you can now also use --analyze to enable esbuild's built-in visualizer. It looks like this:

  $ esbuild --bundle example.jsx --outfile=out.js --minify --analyze
  out.js  27.6kb
  ⚡ Done in 6ms
  out.js                                                                    27.6kb  100.0%
  ├ node_modules/react-dom/cjs/react-dom-server.browser.production.min.js  19.2kb   69.8%
  ├ node_modules/react/cjs/react.production.min.js                          5.9kb   21.4%
  ├ node_modules/object-assign/index.js                                     965b     3.4%
  ├ example.jsx                                                             137b     0.5%
  ├ node_modules/react-dom/server.browser.js                                 50b     0.2%
  └ node_modules/react/index.js                                              50b     0.2%
  

  This tells you what input files were bundled into each output file as well as the final minified size contribution of each input file as well as the percentage of the output file it takes up. You can also enable verbose analysis with --analyze=verbose to see why each input file was included (i.e. which files imported it from the entry point file):

  $ esbuild --bundle example.jsx --outfile=out.js --minify --analyze=verbose
  out.js  27.6kb
  ⚡ Done in 6ms
  out.js ─────────────────────────────────────────────────────────────────── 27.6kb ─ 100.0%
  ├ node_modules/react-dom/cjs/react-dom-server.browser.production.min.js ─ 19.2kb ── 69.8%
  │  └ node_modules/react-dom/server.browser.js
  │     └ example.jsx
  ├ node_modules/react/cjs/react.production.min.js ───────────────────────── 5.9kb ── 21.4%
  │  └ node_modules/react/index.js
  │     └ example.jsx
  ├ node_modules/object-assign/index.js ──────────────────────────────────── 965b ──── 3.4%
  │  └ node_modules/react-dom/cjs/react-dom-server.browser.production.min.js
  │     └ node_modules/react-dom/server.browser.js
  │        └ example.jsx
  ├ example.jsx ──────────────────────────────────────────────────────────── 137b ──── 0.5%
  ├ node_modules/react-dom/server.browser.js ──────────────────────────────── 50b ──── 0.2%
  

... (truncated)

Commits

• 6a3d3a6 publish 0.12.26 to npm
• 2567e09 upgrade "golang.org/x/sys" (#1572)
• ab666a1 fix #1568: release notes for "--analyze"
• c2c2113 add a "verbose" flag to analysis
• 41dbf4d add import paths to analysis
• da15a5f add an "analyze metafile" api
• cfb2938 move "NO_COLOR" handling into the logger itself
• 840a287 release notes for #1579
• 1dea2db feat: Optimizing the __require function (#1580)
• See full diff 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)