chore(deps-dev): bump esbuild from 0.17.0 to 0.17.2

[dependabot]

Bumps esbuild from 0.17.0 to 0.17.2.

Release notes

Sourced from esbuild's releases.

v0.17.2

• Add onDispose to the plugin API (#2140, #2205)

  If your plugin wants to perform some cleanup after it's no longer going to be used, you can now use the onDispose API to register a callback for cleanup-related tasks. For example, if a plugin starts a long-running child process then it may want to terminate that process when the plugin is discarded. Previously there was no way to do this. Here's an example:

  let examplePlugin = {
    name: 'example',
    setup(build) {
      build.onDispose(() => {
        console.log('This plugin is no longer used')
      })
    },
  }

  These onDispose callbacks will be called after every build() call regardless of whether the build failed or not as well as after the first dispose() call on a given build context.

v0.17.1

• Make it possible to cancel a build (#2725)

  The context object introduced in version 0.17.0 has a new cancel() method. You can use it to cancel a long-running build so that you can start a new one without needing to wait for the previous one to finish. When this happens, the previous build should always have at least one error and have no output files (i.e. it will be a failed build).

  Using it might look something like this:

  • JS:

    let ctx = await esbuild.context({
      // ...
    })
    let rebuildWithTimeLimit = timeLimit => {
    let timeout = setTimeout(() => ctx.cancel(), timeLimit)
    return ctx.rebuild().finally(() => clearTimeout(timeout))
    }
    let build = await rebuildWithTimeLimit(500)

  • Go:

    ctx, err := api.Context(api.BuildOptions{
      // ...
    })
    if err != nil {
      return
    }

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.17.2

• Add onDispose to the plugin API (#2140, #2205)

  If your plugin wants to perform some cleanup after it's no longer going to be used, you can now use the onDispose API to register a callback for cleanup-related tasks. For example, if a plugin starts a long-running child process then it may want to terminate that process when the plugin is discarded. Previously there was no way to do this. Here's an example:

  let examplePlugin = {
    name: 'example',
    setup(build) {
      build.onDispose(() => {
        console.log('This plugin is no longer used')
      })
    },
  }

  These onDispose callbacks will be called after every build() call regardless of whether the build failed or not as well as after the first dispose() call on a given build context.

0.17.1

• Make it possible to cancel a build (#2725)

  The context object introduced in version 0.17.0 has a new cancel() method. You can use it to cancel a long-running build so that you can start a new one without needing to wait for the previous one to finish. When this happens, the previous build should always have at least one error and have no output files (i.e. it will be a failed build).

  Using it might look something like this:

  • JS:

    let ctx = await esbuild.context({
      // ...
    })
    let rebuildWithTimeLimit = timeLimit => {
    let timeout = setTimeout(() => ctx.cancel(), timeLimit)
    return ctx.rebuild().finally(() => clearTimeout(timeout))
    }
    let build = await rebuildWithTimeLimit(500)

  • Go:

    ctx, err := api.Context(api.BuildOptions{
      // ...
    })
    if err != nil {
      return

... (truncated)

Commits

• a98870a publish 0.17.2 to npm
• 2163bf6 attempt to work around a ci-only problem
• 1d9e158 attempt to make cancel + rebuild more robust
• 7ba9504 rename waitGroup to disposeWaitGroup
• f0bff33 optimization: skip on-end packet when not needed
• 345ac51 test coverage for js watch output to stdout
• a691c04 test coverage for native watch output to stdout
• a3d3369 semantic change: always run onStart callbacks
• 8ffa1b7 fix rebuildCancel test flakes
• 462b286 add timeout for js tests for debugging ci
• 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)