esbuild 0.25.11

[BrewTestBot]

Created by brew bump

---

Created with brew bump-formula-pr.

release notes

* Add support for `with { type: 'bytes' }` imports ([#4292](https://github.com/evanw/esbuild/issues/4292))
The [import bytes](https://github.com/tc39/proposal-import-bytes) proposal has reached stage 2.7 in the TC39 process, which means that although it isn't quite recommended for implementation, it's generally approved and ready for validation. Furthermore it has already been implemented by [Deno](https://docs.deno.com/examples/importing_bytes/) and [Webpack](https://github.com/webpack/webpack/pull/19928). So with this release, esbuild will also add support for this. It behaves exactly the same as esbuild's existing [`binary` loader](https://esbuild.github.io/content-types/#binary). Here's an example:

```js
import data from './image.png' with { type: 'bytes' }
const view = new DataView(data.buffer, 0, 24)
const width = view.getInt32(16)
const height = view.getInt32(20)
console.log('size:', width + '\xD7' + height)
```



Lower CSS media query range syntax (#3748, #4293)
With this release, esbuild will now transform CSS media query range syntax into equivalent syntax using min-/max- prefixes for older browsers. For example, the following CSS:
@media (640px <= width <= 960px) {
  main {
    display: flex;
  }
}
will be transformed like this with a target such as --target=chrome100 (or more specifically with --supported:media-range=false if desired):
@media (min-width: 640px) and (max-width: 960px) {
  main {
    display: flex;
  }
}
```</pre>
<p>View the full release notes at <a href="https://github.com/evanw/esbuild/releases/tag/v0.25.11">https://github.com/evanw/esbuild/releases/tag/v0.25.11</a>.</p>

---

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Caution

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.