dependabot[bot] opened a new pull request, #134:
URL: https://github.com/apache/arrow-js/pull/134

   Bumps [esbuild](https://github.com/evanw/esbuild) from 0.25.0 to 0.25.5.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/evanw/esbuild/releases";>esbuild's 
releases</a>.</em></p>
   <blockquote>
   <h2>v0.25.5</h2>
   <ul>
   <li>
   <p>Fix a regression with <code>browser</code> in <code>package.json</code> 
(<a href="https://redirect.github.com/evanw/esbuild/issues/4187";>#4187</a>)</p>
   <p>The fix to <a 
href="https://redirect.github.com/evanw/esbuild/issues/4144";>#4144</a> in 
version 0.25.3 introduced a regression that caused <code>browser</code> 
overrides specified in <code>package.json</code> to fail to override relative 
path names that end in a trailing slash. That behavior change affected the 
<code>[email protected]</code> package. This regression has been fixed, and now has 
test coverage.</p>
   </li>
   <li>
   <p>Add support for certain keywords as TypeScript tuple labels (<a 
href="https://redirect.github.com/evanw/esbuild/issues/4192";>#4192</a>)</p>
   <p>Previously esbuild could incorrectly fail to parse certain keywords as 
TypeScript tuple labels that are parsed by the official TypeScript compiler if 
they were followed by a <code>?</code> modifier. These labels included 
<code>function</code>, <code>import</code>, <code>infer</code>, 
<code>new</code>, <code>readonly</code>, and <code>typeof</code>. With this 
release, these keywords will now be parsed correctly. Here's an example of some 
affected code:</p>
   <pre lang="ts"><code>type Foo = [
     value: any,
     readonly?: boolean, // This is now parsed correctly
   ]
   </code></pre>
   </li>
   <li>
   <p>Add CSS prefixes for the <code>stretch</code> sizing value (<a 
href="https://redirect.github.com/evanw/esbuild/issues/4184";>#4184</a>)</p>
   <p>This release adds support for prefixing CSS declarations such as 
<code>div { width: stretch }</code>. That CSS is now transformed into this 
depending on what the <code>--target=</code> setting includes:</p>
   <pre lang="css"><code>div {
     width: -webkit-fill-available;
     width: -moz-available;
     width: stretch;
   }
   </code></pre>
   </li>
   </ul>
   <h2>v0.25.4</h2>
   <ul>
   <li>
   <p>Add simple support for CORS to esbuild's development server (<a 
href="https://redirect.github.com/evanw/esbuild/issues/4125";>#4125</a>)</p>
   <p>Starting with version 0.25.0, esbuild's development server is no longer 
configured to serve cross-origin requests. This was a deliberate change to 
prevent any website you visit from accessing your running esbuild development 
server. However, this change prevented (by design) certain use cases such as 
&quot;debugging in production&quot; by having your production website load code 
from <code>localhost</code> where the esbuild development server is running.</p>
   <p>To enable this use case, esbuild is adding a feature to allow <a 
href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS";>Cross-Origin
 Resource Sharing</a> (a.k.a. CORS) for <a 
href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS#simple_requests";>simple
 requests</a>. Specifically, passing your origin to the new <code>cors</code> 
option will now set the <code>Access-Control-Allow-Origin</code> response 
header when the request has a matching <code>Origin</code> header. Note that 
this currently only works for requests that don't send a preflight 
<code>OPTIONS</code> request, as esbuild's development server doesn't currently 
support <code>OPTIONS</code> requests.</p>
   <p>Some examples:</p>
   <ul>
   <li>
   <p><strong>CLI:</strong></p>
   <pre><code>esbuild --servedir=. --cors-origin=https://example.com
   </code></pre>
   </li>
   <li>
   <p><strong>JS:</strong></p>
   <pre lang="js"><code>const ctx = await esbuild.context({})
   await ctx.serve({
     servedir: '.',
     cors: {
   </code></pre>
   </li>
   </ul>
   </li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/evanw/esbuild/blob/main/CHANGELOG.md";>esbuild's 
changelog</a>.</em></p>
   <blockquote>
   <h2>0.25.5</h2>
   <ul>
   <li>
   <p>Fix a regression with <code>browser</code> in <code>package.json</code> 
(<a href="https://redirect.github.com/evanw/esbuild/issues/4187";>#4187</a>)</p>
   <p>The fix to <a 
href="https://redirect.github.com/evanw/esbuild/issues/4144";>#4144</a> in 
version 0.25.3 introduced a regression that caused <code>browser</code> 
overrides specified in <code>package.json</code> to fail to override relative 
path names that end in a trailing slash. That behavior change affected the 
<code>[email protected]</code> package. This regression has been fixed, and now has 
test coverage.</p>
   </li>
   <li>
   <p>Add support for certain keywords as TypeScript tuple labels (<a 
href="https://redirect.github.com/evanw/esbuild/issues/4192";>#4192</a>)</p>
   <p>Previously esbuild could incorrectly fail to parse certain keywords as 
TypeScript tuple labels that are parsed by the official TypeScript compiler if 
they were followed by a <code>?</code> modifier. These labels included 
<code>function</code>, <code>import</code>, <code>infer</code>, 
<code>new</code>, <code>readonly</code>, and <code>typeof</code>. With this 
release, these keywords will now be parsed correctly. Here's an example of some 
affected code:</p>
   <pre lang="ts"><code>type Foo = [
     value: any,
     readonly?: boolean, // This is now parsed correctly
   ]
   </code></pre>
   </li>
   <li>
   <p>Add CSS prefixes for the <code>stretch</code> sizing value (<a 
href="https://redirect.github.com/evanw/esbuild/issues/4184";>#4184</a>)</p>
   <p>This release adds support for prefixing CSS declarations such as 
<code>div { width: stretch }</code>. That CSS is now transformed into this 
depending on what the <code>--target=</code> setting includes:</p>
   <pre lang="css"><code>div {
     width: -webkit-fill-available;
     width: -moz-available;
     width: stretch;
   }
   </code></pre>
   </li>
   </ul>
   <h2>0.25.4</h2>
   <ul>
   <li>
   <p>Add simple support for CORS to esbuild's development server (<a 
href="https://redirect.github.com/evanw/esbuild/issues/4125";>#4125</a>)</p>
   <p>Starting with version 0.25.0, esbuild's development server is no longer 
configured to serve cross-origin requests. This was a deliberate change to 
prevent any website you visit from accessing your running esbuild development 
server. However, this change prevented (by design) certain use cases such as 
&quot;debugging in production&quot; by having your production website load code 
from <code>localhost</code> where the esbuild development server is running.</p>
   <p>To enable this use case, esbuild is adding a feature to allow <a 
href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS";>Cross-Origin
 Resource Sharing</a> (a.k.a. CORS) for <a 
href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS#simple_requests";>simple
 requests</a>. Specifically, passing your origin to the new <code>cors</code> 
option will now set the <code>Access-Control-Allow-Origin</code> response 
header when the request has a matching <code>Origin</code> header. Note that 
this currently only works for requests that don't send a preflight 
<code>OPTIONS</code> request, as esbuild's development server doesn't currently 
support <code>OPTIONS</code> requests.</p>
   <p>Some examples:</p>
   <ul>
   <li>
   <p><strong>CLI:</strong></p>
   <pre><code>esbuild --servedir=. --cors-origin=https://example.com
   </code></pre>
   </li>
   <li>
   <p><strong>JS:</strong></p>
   <pre lang="js"><code>const ctx = await esbuild.context({})
   await ctx.serve({
   </code></pre>
   </li>
   </ul>
   </li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/evanw/esbuild/commit/ea453bf687c8e5cf3c5f11aae372c5ca33be0c98";><code>ea453bf</code></a>
 publish 0.25.5 to npm</li>
   <li><a 
href="https://github.com/evanw/esbuild/commit/223ddc6a5f1b4721573765eb5b8571888f64313e";><code>223ddc6</code></a>
 fix <a href="https://redirect.github.com/evanw/esbuild/issues/4187";>#4187</a>: 
browser <code>package.json</code> regression</li>
   <li><a 
href="https://github.com/evanw/esbuild/commit/b2c825150b7aa471bcc9b4302ba990557596c35f";><code>b2c8251</code></a>
 fix <a href="https://redirect.github.com/evanw/esbuild/issues/4192";>#4192</a>: 
typescript tuple label parser edge case</li>
   <li><a 
href="https://github.com/evanw/esbuild/commit/28cf2f3e7f4b5b2e629171c0e340fbb406ce68f8";><code>28cf2f3</code></a>
 fix <a href="https://redirect.github.com/evanw/esbuild/issues/4184";>#4184</a>: 
css prefixes for <code>stretch</code></li>
   <li><a 
href="https://github.com/evanw/esbuild/commit/bee1b09cd565fd122c798f57c9617111f7c999ca";><code>bee1b09</code></a>
 fix comment indents</li>
   <li><a 
href="https://github.com/evanw/esbuild/commit/9ddfe5fa15a5e782f8118459a1b8aa3f9f9e87c2";><code>9ddfe5f</code></a>
 run <code>make update-compat-table</code></li>
   <li><a 
href="https://github.com/evanw/esbuild/commit/c339f34484463f597b77c8450c393bfdd26c629e";><code>c339f34</code></a>
 fix a misplaced comment</li>
   <li><a 
href="https://github.com/evanw/esbuild/commit/218d29e9da018d60cf87b8fb496bb8167936ff54";><code>218d29e</code></a>
 publish 0.25.4 to npm</li>
   <li><a 
href="https://github.com/evanw/esbuild/commit/e66cd0bf6daebff56527540c433c69e49e9dcb13";><code>e66cd0b</code></a>
 dev server: simple support for CORS requests (<a 
href="https://redirect.github.com/evanw/esbuild/issues/4171";>#4171</a>)</li>
   <li><a 
href="https://github.com/evanw/esbuild/commit/8bf33685941e857c2b0f10c4d719a895f9d1ceea";><code>8bf3368</code></a>
 js api: validate some options as arrays of strings</li>
   <li>Additional commits viewable in <a 
href="https://github.com/evanw/esbuild/compare/v0.25.0...v0.25.5";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=esbuild&package-manager=npm_and_yarn&previous-version=0.25.0&new-version=0.25.5)](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>
   <br />
   
   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 show <dependency name> ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@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>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to