Bump esbuild from 0.16.14 to 0.17.0 #344

Closed

dependabot[bot] wants to merge 1 commit from dependabot/npm_and_yarn/esbuild-0.17.0 into master

dependabot[bot] commented

2023-01-16 11:07:13 +01:00

(Migrated from github.com)

Bumps esbuild from 0.16.14 to 0.17.0.

Release notes

Sourced from esbuild's releases.

v0.17.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.16.0 or ~0.16.0. See npm's documentation about semver for more information.

At a high level, the breaking changes in this release fix some long-standing issues with the design of esbuild's incremental, watch, and serve APIs. This release also introduces some exciting new features such as live reloading. In detail:
Move everything related to incremental builds to a new context API (#1037, #1606, #2280, #2418)

This change removes the incremental and watch options as well as the serve() method, and introduces a new context() method. The context method takes the same arguments as the build() method but only validates its arguments and does not do an initial build. Instead, builds can be triggered using the rebuild(), watch(), and serve() methods on the returned context object. The new context API looks like this:
// Create a context for incremental builds
const context = await esbuild.context({
  entryPoints: ['app.ts'],
  bundle: true,
})
// Manually do an incremental build
const result = await context.rebuild()
// Enable watch mode
await context.watch()
// Enable serve mode
await context.serve()
// Dispose of the context
context.dispose()
The switch to the context API solves a major issue with the previous API which is that if the initial build fails, a promise is thrown in JavaScript which prevents you from accessing the returned result object. That prevented you from setting up long-running operations such as watch mode when the initial build contained errors. It also makes tearing down incremental builds simpler as there is now a single way to do it instead of three separate ways.

In addition, this release also makes some subtle changes to how incremental builds work. Previously every call to rebuild() started a new build. If you weren't careful, then builds could actually overlap. This doesn't cause any problems with esbuild itself, but could potentially cause problems with plugins (esbuild doesn't even give you a way to identify which overlapping build a given plugin callback is running on). Overlapping builds also arguably aren't useful, or at least aren't useful enough to justify the confusion and complexity that they bring. With this release, there is now only ever a single active build per context. Calling rebuild() before the previous rebuild has finished now "merges" with the existing rebuild instead of starting a new build.
Allow using watch and serve together (#805, #1650, #2576)

Previously it was not possible to use watch mode and serve mode together. The rationale was that watch mode is one way of automatically rebuilding your project and serve mode is another (since serve mode automatically rebuilds on every request). However, people want to combine these two features to make "live reloading" where the browser automatically reloads the page when files are changed on the file system.

This release now allows you to use these two features together. You can only call the watch() and serve() APIs once each per context, but if you call them together on the same context then esbuild will automatically rebuild both when files on the file system are changed and when the server serves a request.
Support "live reloading" through server-sent events (#802)

Server-sent events are a simple way to pass one-directional messages asynchronously from the server to the client. Serve mode now provides a /esbuild endpoint with an change event that triggers every time esbuild's output changes. So you can now implement simple "live reloading" (i.e. reloading the page when a file is edited and saved) like this:
new EventSource('/esbuild').addEventListener('change', () => location.reload())
The event payload is a JSON object with the following shape:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.17.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.16.0 or ~0.16.0. See npm's documentation about semver for more information.

At a high level, the breaking changes in this release fix some long-standing issues with the design of esbuild's incremental, watch, and serve APIs. This release also introduces some exciting new features such as live reloading. In detail:
Move everything related to incremental builds to a new context API (#1037, #1606, #2280, #2418)

This change removes the incremental and watch options as well as the serve() method, and introduces a new context() method. The context method takes the same arguments as the build() method but only validates its arguments and does not do an initial build. Instead, builds can be triggered using the rebuild(), watch(), and serve() methods on the returned context object. The new context API looks like this:
// Create a context for incremental builds
const context = await esbuild.context({
  entryPoints: ['app.ts'],
  bundle: true,
})
// Manually do an incremental build
const result = await context.rebuild()
// Enable watch mode
await context.watch()
// Enable serve mode
await context.serve()
// Dispose of the context
context.dispose()
The switch to the context API solves a major issue with the previous API which is that if the initial build fails, a promise is thrown in JavaScript which prevents you from accessing the returned result object. That prevented you from setting up long-running operations such as watch mode when the initial build contained errors. It also makes tearing down incremental builds simpler as there is now a single way to do it instead of three separate ways.

In addition, this release also makes some subtle changes to how incremental builds work. Previously every call to rebuild() started a new build. If you weren't careful, then builds could actually overlap. This doesn't cause any problems with esbuild itself, but could potentially cause problems with plugins (esbuild doesn't even give you a way to identify which overlapping build a given plugin callback is running on). Overlapping builds also arguably aren't useful, or at least aren't useful enough to justify the confusion and complexity that they bring. With this release, there is now only ever a single active build per context. Calling rebuild() before the previous rebuild has finished now "merges" with the existing rebuild instead of starting a new build.
Allow using watch and serve together (#805, #1650, #2576)

Previously it was not possible to use watch mode and serve mode together. The rationale was that watch mode is one way of automatically rebuilding your project and serve mode is another (since serve mode automatically rebuilds on every request). However, people want to combine these two features to make "live reloading" where the browser automatically reloads the page when files are changed on the file system.

This release now allows you to use these two features together. You can only call the watch() and serve() APIs once each per context, but if you call them together on the same context then esbuild will automatically rebuild both when files on the file system are changed and when the server serves a request.
Support "live reloading" through server-sent events (#802)

Server-sent events are a simple way to pass one-directional messages asynchronously from the server to the client. Serve mode now provides a /esbuild endpoint with an change event that triggers every time esbuild's output changes. So you can now implement simple "live reloading" (i.e. reloading the page when a file is edited and saved) like this:
new EventSource('/esbuild').addEventListener('change', () => location.reload())
The event payload is a JSON object with the following shape:

... (truncated)

Commits

2a18b3d publish 0.17.0 to npm
60ba46a test coverage for build merging
3153032 Version 0.17.0: rewrite the incremental build apis (#2816)
5579b0f change wordmark text
fa27e29 fix link to go docs
e72962f Update README.md
5d80704 new year new changelog
9cc2b84 add more info to exports errors in package.json
d751dfb publish 0.16.17 to npm
6346398 fix #2814: additional comment-related regressions
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)

Bumps [esbuild](https://github.com/evanw/esbuild) from 0.16.14 to 0.17.0. <details> <summary>Release notes</summary> Sourced from <a href="https://github.com/evanw/esbuild/releases">esbuild's releases</a>. <blockquote> <h2>v0.17.0</h2> This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of <code>esbuild</code> in your <code>package.json</code> file (recommended) or be using a version range syntax that only accepts patch upgrades such as <code>^0.16.0</code> or <code>~0.16.0</code>. See npm's documentation about <a href="https://docs.npmjs.com/cli/v6/using-npm/semver/">semver</a> for more information. At a high level, the breaking changes in this release fix some long-standing issues with the design of esbuild's incremental, watch, and serve APIs. This release also introduces some exciting new features such as live reloading. In detail: <ul> <li> Move everything related to incremental builds to a new <code>context</code> API (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/1037">#1037</a>, <a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/1606">#1606</a>, <a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2280">#2280</a>, <a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2418">#2418</a>) This change removes the <code>incremental</code> and <code>watch</code> options as well as the <code>serve()</code> method, and introduces a new <code>context()</code> method. The context method takes the same arguments as the <code>build()</code> method but only validates its arguments and does not do an initial build. Instead, builds can be triggered using the <code>rebuild()</code>, <code>watch()</code>, and <code>serve()</code> methods on the returned context object. The new context API looks like this: <pre lang="js"><code>// Create a context for incremental builds const context = await esbuild.context({ entryPoints: ['app.ts'], bundle: true, }) // Manually do an incremental build const result = await context.rebuild() // Enable watch mode await context.watch() // Enable serve mode await context.serve() // Dispose of the context context.dispose() </code></pre> The switch to the context API solves a major issue with the previous API which is that if the initial build fails, a promise is thrown in JavaScript which prevents you from accessing the returned result object. That prevented you from setting up long-running operations such as watch mode when the initial build contained errors. It also makes tearing down incremental builds simpler as there is now a single way to do it instead of three separate ways. In addition, this release also makes some subtle changes to how incremental builds work. Previously every call to <code>rebuild()</code> started a new build. If you weren't careful, then builds could actually overlap. This doesn't cause any problems with esbuild itself, but could potentially cause problems with plugins (esbuild doesn't even give you a way to identify which overlapping build a given plugin callback is running on). Overlapping builds also arguably aren't useful, or at least aren't useful enough to justify the confusion and complexity that they bring. With this release, there is now only ever a single active build per context. Calling <code>rebuild()</code> before the previous rebuild has finished now "merges" with the existing rebuild instead of starting a new build. </li> <li> Allow using <code>watch</code> and <code>serve</code> together (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/805">#805</a>, <a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/1650">#1650</a>, <a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2576">#2576</a>) Previously it was not possible to use watch mode and serve mode together. The rationale was that watch mode is one way of automatically rebuilding your project and serve mode is another (since serve mode automatically rebuilds on every request). However, people want to combine these two features to make "live reloading" where the browser automatically reloads the page when files are changed on the file system. This release now allows you to use these two features together. You can only call the <code>watch()</code> and <code>serve()</code> APIs once each per context, but if you call them together on the same context then esbuild will automatically rebuild both when files on the file system are changed and when the server serves a request. </li> <li> Support "live reloading" through server-sent events (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/802">#802</a>) <a href="https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events">Server-sent events</a> are a simple way to pass one-directional messages asynchronously from the server to the client. Serve mode now provides a <code>/esbuild</code> endpoint with an <code>change</code> event that triggers every time esbuild's output changes. So you can now implement simple "live reloading" (i.e. reloading the page when a file is edited and saved) like this: <pre lang="js"><code>new EventSource('/esbuild').addEventListener('change', () => location.reload()) </code></pre> The event payload is a JSON object with the following shape: <pre lang="ts"><code></code></pre> </li> </ul>  </blockquote> ... (truncated) </details> <details> <summary>Changelog</summary> Sourced from <a href="https://github.com/evanw/esbuild/blob/main/CHANGELOG.md">esbuild's changelog</a>. <blockquote> <h2>0.17.0</h2> This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of <code>esbuild</code> in your <code>package.json</code> file (recommended) or be using a version range syntax that only accepts patch upgrades such as <code>^0.16.0</code> or <code>~0.16.0</code>. See npm's documentation about <a href="https://docs.npmjs.com/cli/v6/using-npm/semver/">semver</a> for more information. At a high level, the breaking changes in this release fix some long-standing issues with the design of esbuild's incremental, watch, and serve APIs. This release also introduces some exciting new features such as live reloading. In detail: <ul> <li> Move everything related to incremental builds to a new <code>context</code> API (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/1037">#1037</a>, <a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/1606">#1606</a>, <a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2280">#2280</a>, <a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2418">#2418</a>) This change removes the <code>incremental</code> and <code>watch</code> options as well as the <code>serve()</code> method, and introduces a new <code>context()</code> method. The context method takes the same arguments as the <code>build()</code> method but only validates its arguments and does not do an initial build. Instead, builds can be triggered using the <code>rebuild()</code>, <code>watch()</code>, and <code>serve()</code> methods on the returned context object. The new context API looks like this: <pre lang="js"><code>// Create a context for incremental builds const context = await esbuild.context({ entryPoints: ['app.ts'], bundle: true, }) // Manually do an incremental build const result = await context.rebuild() // Enable watch mode await context.watch() // Enable serve mode await context.serve() // Dispose of the context context.dispose() </code></pre> The switch to the context API solves a major issue with the previous API which is that if the initial build fails, a promise is thrown in JavaScript which prevents you from accessing the returned result object. That prevented you from setting up long-running operations such as watch mode when the initial build contained errors. It also makes tearing down incremental builds simpler as there is now a single way to do it instead of three separate ways. In addition, this release also makes some subtle changes to how incremental builds work. Previously every call to <code>rebuild()</code> started a new build. If you weren't careful, then builds could actually overlap. This doesn't cause any problems with esbuild itself, but could potentially cause problems with plugins (esbuild doesn't even give you a way to identify which overlapping build a given plugin callback is running on). Overlapping builds also arguably aren't useful, or at least aren't useful enough to justify the confusion and complexity that they bring. With this release, there is now only ever a single active build per context. Calling <code>rebuild()</code> before the previous rebuild has finished now "merges" with the existing rebuild instead of starting a new build. </li> <li> Allow using <code>watch</code> and <code>serve</code> together (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/805">#805</a>, <a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/1650">#1650</a>, <a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2576">#2576</a>) Previously it was not possible to use watch mode and serve mode together. The rationale was that watch mode is one way of automatically rebuilding your project and serve mode is another (since serve mode automatically rebuilds on every request). However, people want to combine these two features to make "live reloading" where the browser automatically reloads the page when files are changed on the file system. This release now allows you to use these two features together. You can only call the <code>watch()</code> and <code>serve()</code> APIs once each per context, but if you call them together on the same context then esbuild will automatically rebuild both when files on the file system are changed and when the server serves a request. </li> <li> Support "live reloading" through server-sent events (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/802">#802</a>) <a href="https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events">Server-sent events</a> are a simple way to pass one-directional messages asynchronously from the server to the client. Serve mode now provides a <code>/esbuild</code> endpoint with an <code>change</code> event that triggers every time esbuild's output changes. So you can now implement simple "live reloading" (i.e. reloading the page when a file is edited and saved) like this: <pre lang="js"><code>new EventSource('/esbuild').addEventListener('change', () => location.reload()) </code></pre> The event payload is a JSON object with the following shape: </li> </ul>  </blockquote> ... (truncated) </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/evanw/esbuild/commit/2a18b3d6ab3d1003afbcfcb4a6ffca61e04fcb57"><code>2a18b3d</code></a> publish 0.17.0 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/60ba46a3df646d82328a340da75f90f7b9a4af41"><code>60ba46a</code></a> test coverage for build merging</li> <li><a href="https://github.com/evanw/esbuild/commit/3153032c7d0ea1874688d49e0fd943f577f93cb5"><code>3153032</code></a> Version 0.17.0: rewrite the incremental build apis (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2816">#2816</a>)</li> <li><a href="https://github.com/evanw/esbuild/commit/5579b0f62229970ff8b437ad7280fe7149ba9a2f"><code>5579b0f</code></a> change wordmark text</li> <li><a href="https://github.com/evanw/esbuild/commit/fa27e29bd5203f46827575f2ab980f15fad15e8d"><code>fa27e29</code></a> fix link to go docs</li> <li><a href="https://github.com/evanw/esbuild/commit/e72962f7e9e76e5d69290aa7e2c32d8b2acfdbbb"><code>e72962f</code></a> Update README.md</li> <li><a href="https://github.com/evanw/esbuild/commit/5d80704f1c64213da83c5f18d6f95255ccdff86e"><code>5d80704</code></a> new year new changelog</li> <li><a href="https://github.com/evanw/esbuild/commit/9cc2b84f9db77c0f6489613809cd081c3400ea9e"><code>9cc2b84</code></a> add more info to <code>exports</code> errors in package.json</li> <li><a href="https://github.com/evanw/esbuild/commit/d751dfb82002d332aa4dbfa89c74d25203d28123"><code>d751dfb</code></a> publish 0.16.17 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/6346398851a3231a8c4b31f8a608d0888272f239"><code>6346398</code></a> fix <a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2814">#2814</a>: additional comment-related regressions</li> <li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.16.14...v0.17.0">compare view</a></li> </ul> </details> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=esbuild&package-manager=npm_and_yarn&previous-version=0.16.14&new-version=0.17.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> 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) </details>

dependabot[bot] commented

2023-01-17 11:04:54 +01:00

(Migrated from github.com)

Superseded by #345.

Commenting is not possible because the repository is archived.

No reviewers