Bump esbuild from 0.16.17 to 0.17.1

[dependabot]

Bumps esbuild from 0.16.17 to 0.17.1.

Release notes

Sourced from esbuild's releases.

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
    }
    rebuildWithTimeLimit := func(timeLimit time.Duration) api.BuildResult {
    t := time.NewTimer(timeLimit)
    go func() {
    <-t.C
    ctx.Cancel()
    }()
    result := ctx.Rebuild()
    t.Stop()
    return result
    }
    build := rebuildWithTimeLimit(500 * time.Millisecond)

  This API is a quick implementation and isn't maximally efficient, so the build may continue to do some work for a little bit before stopping. For example, I have added stop points between each top-level phase of the bundler and in the main module graph traversal loop, but I haven't added fine-grained stop points within the internals of the linker. How quickly esbuild stops can be improved in future releases. This means you'll want to wait for cancel() and/or the previous rebuild() to finish (i.e. await the returned promise in JavaScript) before starting a new build, otherwise rebuild() will give you the just-canceled build that still hasn't ended yet. Note that onEnd callbacks will still be run regardless of whether or not the build was canceled.

• Fix server-sent events without servedir (#2827)

... (truncated)

Changelog

Sourced from esbuild's changelog.

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
    }
    rebuildWithTimeLimit := func(timeLimit time.Duration) api.BuildResult {
    t := time.NewTimer(timeLimit)
    go func() {
    <-t.C
    ctx.Cancel()
    }()
    result := ctx.Rebuild()
    t.Stop()
    return result
    }
    build := rebuildWithTimeLimit(500 * time.Millisecond)

  This API is a quick implementation and isn't maximally efficient, so the build may continue to do some work for a little bit before stopping. For example, I have added stop points between each top-level phase of the bundler and in the main module graph traversal loop, but I haven't added fine-grained stop points within the internals of the linker. How quickly esbuild stops can be improved in future releases. This means you'll want to wait for cancel() and/or the previous rebuild() to finish (i.e. await the returned promise in JavaScript) before starting a new build, otherwise rebuild() will give you the just-canceled build that still hasn't ended yet. Note that onEnd callbacks will still be run regardless of whether or not the build was canceled.

• Fix server-sent events without servedir (#2827)

... (truncated)

Commits

• 002ef95 publish 0.17.1 to npm
• 19cc14d avoid apis added in go 1.19
• 232f4b9 go only lets you close a channel once
• e4377c1 fix #2725: make it possible to cancel a build
• 01efc05 follow-up to #2828: duplicate custom output paths
• 5a586ab use fewer semicolons in js/ts code
• 4776064 update links in documentation comments
• 60c0f9d fix bad outfile in test
• 5b8235f fix #2828: copy loader + custom output paths
• f12d93c fix #2827: live reload broken without servedir
• 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)