Bump esbuild from 0.8.57 to 0.14.18

[dependabot[bot]]

Bumps esbuild from 0.8.57 to 0.14.18.

Release notes

Sourced from esbuild's releases.

v0.14.18

• Add the --mangle-cache= feature (#1977)

  This release adds a cache API for the newly-released --mangle-props= feature. When enabled, all mangled property renamings are recorded in the cache during the initial build. Subsequent builds reuse the renamings stored in the cache and add additional renamings for any newly-added properties. This has a few consequences:

  • You can customize what mangled properties are renamed to by editing the cache before passing it to esbuild (the cache is a map of the original name to the mangled name).

  • The cache serves as a list of all properties that were mangled. You can easily scan it to see if there are any unexpected property renamings.

  • You can disable mangling for individual properties by setting the renamed value to false instead of to a string. This is similar to the --reserve-props= setting but on a per-property basis.

  • You can ensure consistent renaming between builds (e.g. a main-thread file and a web worker, or a library and a plugin). Without this feature, each build would do an independent renaming operation and the mangled property names likely wouldn't be consistent.

  Here's how to use it:

  • CLI

    $ esbuild example.ts --mangle-props=_$ --mangle-cache=cache.json
    

  • JS API

    let result = await esbuild.build({
      entryPoints: ['example.ts'],
      mangleProps: /_$/,
      mangleCache: {
        customRenaming_: '__c',
        disabledRenaming_: false,
      },
    })
    let updatedMangleCache = result.mangleCache
    

  • Go API

    result := api.Build(api.BuildOptions{
      EntryPoints: []string{"example.ts"},
      MangleProps: "_$",
      MangleCache: map[string]interface{}{
        "customRenaming_":   "__c",
        "disabledRenaming_": false,
      },
    })
    updatedMangleCache := result.MangleCache
    

  The above code would do something like the following:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.14.18

• Add the --mangle-cache= feature (#1977)

  This release adds a cache API for the newly-released --mangle-props= feature. When enabled, all mangled property renamings are recorded in the cache during the initial build. Subsequent builds reuse the renamings stored in the cache and add additional renamings for any newly-added properties. This has a few consequences:

  • You can customize what mangled properties are renamed to by editing the cache before passing it to esbuild (the cache is a map of the original name to the mangled name).

  • The cache serves as a list of all properties that were mangled. You can easily scan it to see if there are any unexpected property renamings.

  • You can disable mangling for individual properties by setting the renamed value to false instead of to a string. This is similar to the --reserve-props= setting but on a per-property basis.

  • You can ensure consistent renaming between builds (e.g. a main-thread file and a web worker, or a library and a plugin). Without this feature, each build would do an independent renaming operation and the mangled property names likely wouldn't be consistent.

  Here's how to use it:

  • CLI

    $ esbuild example.ts --mangle-props=_$ --mangle-cache=cache.json
    

  • JS API

    let result = await esbuild.build({
      entryPoints: ['example.ts'],
      mangleProps: /_$/,
      mangleCache: {
        customRenaming_: '__c',
        disabledRenaming_: false,
      },
    })
    let updatedMangleCache = result.mangleCache
    

  • Go API

    result := api.Build(api.BuildOptions{
      EntryPoints: []string{"example.ts"},
      MangleProps: "_$",
      MangleCache: map[string]interface{}{
        "customRenaming_":   "__c",
        "disabledRenaming_": false,
      },
    })
    updatedMangleCache := result.MangleCache
    

... (truncated)

Commits

• 049e765 publish 0.14.18 to npm
• 81215bc minify undefined checks to typeof x < u
• 3108405 add ie to browser feature table
• fdb3e9d add opera to browser feature table
• 8e81f43 update from go 1.17.5 to go 1.17.6
• 02894dc fix #1977: add the --mangle-cache= feature
• fc45394 cli: clean up extra return value code
• eba56ee internal minify flags now match external flags
• 43a7ce6 publish 0.14.17 to npm
• 54ebf0c fix #1711: attempt to fix install script with snap
• 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)

[dependabot[bot]]

Superseded by #120.