build(deps-dev): bump esbuild from 0.11.2 to 0.11.3

[dependabot]

Bumps esbuild from 0.11.2 to 0.11.3.

Release notes

Sourced from esbuild's releases.

v0.11.3

• Auto-define process.env.NODE_ENV when platform is set to browser

  All code in the React world has the requirement that the specific expression process.env.NODE_ENV must be replaced with a string at compile-time or your code will immediately crash at run-time. This is a common stumbling point for people when they start using esbuild with React. Previously bundling code with esbuild containing process.env.NODE_ENV without defining a string replacement first was a warning that warned you about the lack of a define.

  With this release esbuild will now attempt to define process.env.NODE_ENV automatically instead of warning about it. This will be implicitly defined to "production" if minification is enabled and "development" otherwise. This automatic behavior only happens when the platform is browser, since process is not a valid browser API and will never exist in the browser. This is also only done if there are no existing defines for process, process.env, or process.env.NODE_ENV so you can override the automatic value if necessary. If you need to disable this behavior, you can use the neutral platform instead of the browser platform.

• Retain side-effect free intermediate re-exporting files (#1088)

  This fixes a subtle bug with esbuild's support for Webpack's "sideEffects": false annotation in package.json when combined with re-export statements. A re-export is when you import something from one file and then export it again. You can re-export something with export * from or export {foo} from or import {foo} from followed by export {foo}.

  The bug was that files which only contain re-exports and that are marked as being side-effect free were not being included in the bundle if you import one of the re-exported symbols. This is because esbuild's implementation of re-export linking caused the original importing file to "short circuit" the re-export and just import straight from the file containing the final symbol, skipping the file containing the re-export entirely.

  This was normally not observable since the intermediate file consisted entirely of re-exports, which have no side effects. However, a recent change to allow ESM files to be lazily-initialized relies on all intermediate files being included in the bundle to trigger the initialization of the lazy evaluation wrappers. So the behavior of skipping over re-export files is now causing the imported symbols to not be initialized if the re-exported file is marked as lazily-evaluated.

  The fix is to track all re-exports in the import chain from the original file to the file containing the final symbol and then retain all of those statements if the import ends up being used.

• Add a very verbose debug log level

  This log level is an experiment. Enabling it logs a lot of information (currently only about path resolution). The idea is that if you are having an obscure issue, the debug log level might contain some useful information. Unlike normal logs which are meant to mainly provide actionable information, these debug logs are intentionally mostly noise and are designed to be searched through instead.

  Here is an example of debug-level log output:

   > debug: Resolving import "react" in directory "src" of type "import-statement"
     note: Read 26 entries for directory "src"
     note: Searching for "react" in "node_modules" directories starting from "src"
     note: Attempting to load "src/react" as a file
     note: Failed to find file "src/react"
     note: Failed to find file "src/react.tsx"
     note: Failed to find file "src/react.ts"
     note: Failed to find file "src/react.js"
     note: Failed to find file "src/react.css"
     note: Failed to find file "src/react.svg"
     note: Attempting to load "src/react" as a directory
     note: Failed to read directory "src/react"
     note: Parsed package name "react" and package subpath "."
     note: Checking for a package in the directory "node_modules/react"
     note: Read 7 entries for directory "node_modules/react"
     note: Read 393 entries for directory "node_modules"
     note: Attempting to load "node_modules/react" as a file
     note: Failed to find file "node_modules/react"
     note: Failed to find file "node_modules/react.tsx"
     note: Failed to find file "node_modules/react.ts"
     note: Failed to find file "node_modules/react.js"
     note: Failed to find file "node_modules/react.css"
     note: Failed to find file "node_modules/react.svg"
     note: Attempting to load "node_modules/react" as a directory
     note: Read 7 entries for directory "node_modules/react"
     note: Resolved to "node_modules/react/index.js" using the "main" field in "node_modules/react/package.json"
  

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.11.3

• Auto-define process.env.NODE_ENV when platform is set to browser

  All code in the React world has the requirement that the specific expression process.env.NODE_ENV must be replaced with a string at compile-time or your code will immediately crash at run-time. This is a common stumbling point for people when they start using esbuild with React. Previously bundling code with esbuild containing process.env.NODE_ENV without defining a string replacement first was a warning that warned you about the lack of a define.

  With this release esbuild will now attempt to define process.env.NODE_ENV automatically instead of warning about it. This will be implicitly defined to "production" if minification is enabled and "development" otherwise. This automatic behavior only happens when the platform is browser, since process is not a valid browser API and will never exist in the browser. This is also only done if there are no existing defines for process, process.env, or process.env.NODE_ENV so you can override the automatic value if necessary. If you need to disable this behavior, you can use the neutral platform instead of the browser platform.

• Retain side-effect free intermediate re-exporting files (#1088)

  This fixes a subtle bug with esbuild's support for Webpack's "sideEffects": false annotation in package.json when combined with re-export statements. A re-export is when you import something from one file and then export it again. You can re-export something with export * from or export {foo} from or import {foo} from followed by export {foo}.

  The bug was that files which only contain re-exports and that are marked as being side-effect free were not being included in the bundle if you import one of the re-exported symbols. This is because esbuild's implementation of re-export linking caused the original importing file to "short circuit" the re-export and just import straight from the file containing the final symbol, skipping the file containing the re-export entirely.

  This was normally not observable since the intermediate file consisted entirely of re-exports, which have no side effects. However, a recent change to allow ESM files to be lazily-initialized relies on all intermediate files being included in the bundle to trigger the initialization of the lazy evaluation wrappers. So the behavior of skipping over re-export files is now causing the imported symbols to not be initialized if the re-exported file is marked as lazily-evaluated.

  The fix is to track all re-exports in the import chain from the original file to the file containing the final symbol and then retain all of those statements if the import ends up being used.

• Add a very verbose debug log level

  This log level is an experiment. Enabling it logs a lot of information (currently only about path resolution). The idea is that if you are having an obscure issue, the debug log level might contain some useful information. Unlike normal logs which are meant to mainly provide actionable information, these debug logs are intentionally mostly noise and are designed to be searched through instead.

  Here is an example of debug-level log output:

   > debug: Resolving import "react" in directory "src" of type "import-statement"
     note: Read 26 entries for directory "src"
     note: Searching for "react" in "node_modules" directories starting from "src"
     note: Attempting to load "src/react" as a file
     note: Failed to find file "src/react"
     note: Failed to find file "src/react.tsx"
     note: Failed to find file "src/react.ts"
     note: Failed to find file "src/react.js"
     note: Failed to find file "src/react.css"
     note: Failed to find file "src/react.svg"
     note: Attempting to load "src/react" as a directory
     note: Failed to read directory "src/react"
     note: Parsed package name "react" and package subpath "."
     note: Checking for a package in the directory "node_modules/react"
     note: Read 7 entries for directory "node_modules/react"
     note: Read 393 entries for directory "node_modules"
     note: Attempting to load "node_modules/react" as a file
     note: Failed to find file "node_modules/react"
     note: Failed to find file "node_modules/react.tsx"
     note: Failed to find file "node_modules/react.ts"
     note: Failed to find file "node_modules/react.js"
     note: Failed to find file "node_modules/react.css"
     note: Failed to find file "node_modules/react.svg"
     note: Attempting to load "node_modules/react" as a directory
     note: Read 7 entries for directory "node_modules/react"
  

... (truncated)

Commits

• fb8681e publish 0.11.3 to npm
• c62d33f release notes for "debug" log level
• 76f677c add basic bracketing of bundle phases
• 31b183c add debug logging to resolver
• 5b84d0e insert "resolverQuery" for resolver internals
• 9c4979f add a "debug" log level
• c52f9fd merge "localDependencies" + "nonLocalDependencies"
• 6f6b060 track and retain intermediate re-exporting files (#1100)
• 28fd1a2 dark mode for graph debugger
• 62e3bc0 rename "importToBind" => "importData"
• 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)