starred/gitea-mirror
1
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-04-25 07:15:57 +03:00
Code Issues 11 Projects Releases 10 Packages Wiki Activity

[PR #78] [CLOSED] Bump the npm_and_yarn group across 2 directories with 3 updates #123

New issue
Closed
opened 2026-02-27 15:55:13 +03:00 by kerem · 0 comments
kerem commented 2026-02-27 15:55:13 +03:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/RayLabsHQ/gitea-mirror/pull/78
Author: @dependabot[bot]
Created: 8/20/2025
Status: ❌ Closed

Base: main ← Head: dependabot/npm_and_yarn/npm_and_yarn-4c1cf44590

📝 Commits (1)

  • 52507d5 Bump the npm_and_yarn group across 2 directories with 3 updates

📊 Changes

3 files changed (+426 additions, -296 deletions)

View changed files

📝 package.json (+2 -2)
📝 www/package.json (+1 -1)
📝 www/pnpm-lock.yaml (+423 -293)

📄 Description

Bumps the npm_and_yarn group with 2 updates in the / directory: @astrojs/node and astro.
Bumps the npm_and_yarn group with 1 update in the /www directory: astro.

Updates @astrojs/node from 9.3.3 to 9.4.1

Release notes

Sourced from @​astrojs/node's releases.

@​astrojs/node@​9.4.1

Patch Changes

  • 5fc3c59 Thanks @​ematipico! - Fixes a routing bug in standalone mode with trailingSlash set to "always".

@​astrojs/node@​9.4.0

Minor Changes

  • #14188 e3422aa Thanks @​ascorbic! - Adds support for specifying a host to load prerendered error pages

    By default, if a user defines a custom error page that is prerendered, Astro will load it from the same host as the one that the request is made to. This change allows users to specify a different host for loading prerendered error pages. This can be useful in scenarios such as where the server is running behind a reverse proxy or when prerendered pages are hosted on a different domain.

    To use this feature, set the experimentalErrorPageHost adapter option in your Astro configuration to the desired host URL. For example, if your server is running on localhost and served via a proxy, you can ensure the prerendered error pages are fetched via the localhost URL:

    import { defineConfig } from 'astro/config';
import node from '@astrojs/node';
export default defineConfig({
  adapter: node({
    // If your server is running on localhost and served via a proxy, set the host like this to ensure prerendered error pages are fetched via the localhost URL
    experimentalErrorPageHost: 'http://localhost:4321',
  }),
});

    For more information on enabling and using this experimental feature, see the @astrojs/node adapter docs.

Changelog

Sourced from @​astrojs/node's changelog.

9.4.1

Patch Changes

  • 5fc3c59 Thanks @​ematipico! - Fixes a routing bug in standalone mode with trailingSlash set to "always".

9.4.0

Minor Changes

  • #14188 e3422aa Thanks @​ascorbic! - Adds support for specifying a host to load prerendered error pages

    By default, if a user defines a custom error page that is prerendered, Astro will load it from the same host as the one that the request is made to. This change allows users to specify a different host for loading prerendered error pages. This can be useful in scenarios such as where the server is running behind a reverse proxy or when prerendered pages are hosted on a different domain.

    To use this feature, set the experimentalErrorPageHost adapter option in your Astro configuration to the desired host URL. For example, if your server is running on localhost and served via a proxy, you can ensure the prerendered error pages are fetched via the localhost URL:

    import { defineConfig } from 'astro/config';
import node from '@astrojs/node';
export default defineConfig({
  adapter: node({
    // If your server is running on localhost and served via a proxy, set the host like this to ensure prerendered error pages are fetched via the localhost URL
    experimentalErrorPageHost: 'http://localhost:4321',
  }),
});

    For more information on enabling and using this experimental feature, see the @astrojs/node adapter docs.

Commits

Updates astro from 5.12.8 to 5.13.2

Release notes

Sourced from astro's releases.

astro@5.13.2

Patch Changes

  • 4d16de7 Thanks @​ematipico! - Improves the detection of remote paths in the _image endpoint. Now href parameters that start with // are considered remote paths.

  • Updated dependencies [4d16de7]:

    • @​astrojs/internal-helpers@​0.7.2
    • @​astrojs/markdown-remark@​6.3.6

astro@5.13.1

Patch Changes

astro@5.13.0

Minor Changes

  • #14173 39911b8 Thanks @​florian-lefebvre! - Adds an experimental flag staticImportMetaEnv to disable the replacement of import.meta.env values with process.env calls and their coercion of environment variable values. This supersedes the rawEnvValues experimental flag, which is now removed.

    Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via astro:env into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.

    However, you can still access environment variables through process.env and import.meta.env directly when needed. This was the only way to use environment variables in Astro before astro:env was added in Astro 5.0, and Astro's default handling of import.meta.env includes some logic that was only needed for earlier versions of Astro.

    The experimental.staticImportMetaEnv flag updates the behavior of import.meta.env to align with Vite's handling of environment variables and for better ease of use with Astro's current implementations and features. This will become the default behavior in Astro 6.0, and this early preview is introduced as an experimental feature.

    Currently, non-public import.meta.env environment variables are replaced by a reference to process.env. Additionally, Astro may also convert the value type of your environment variables used through import.meta.env, which can prevent access to some values such as the strings "true" (which is converted to a boolean value), and "1" (which is converted to a number).

    The experimental.staticImportMetaEnv flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any import.meta.env environment variables with a process.env call, nor will it coerce values.

    To enable this feature, add the experimental flag in your Astro config and remove rawEnvValues if it was enabled:

    // astro.config.mjs
import { defineConfig } from "astro/config";

    export default defineConfig({
    

      

    • experimental: {
      • 

    • staticImportMetaEnv: true
      • 

    

      

    • rawEnvValues: false
      • 

    

      

    • }
});

Updating your project

If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:

// src/components/MyComponent.astro
- const enabled: boolean = import.meta.env.ENABLED;

... (truncated)

Changelog

Sourced from astro's changelog.

5.13.2

Patch Changes

  • 4d16de7 Thanks @​ematipico! - Improves the detection of remote paths in the _image endpoint. Now href parameters that start with // are considered remote paths.

  • Updated dependencies [4d16de7]:

    • @​astrojs/internal-helpers@​0.7.2
    • @​astrojs/markdown-remark@​6.3.6

5.13.1

Patch Changes

5.13.0

Minor Changes

  • #14173 39911b8 Thanks @​florian-lefebvre! - Adds an experimental flag staticImportMetaEnv to disable the replacement of import.meta.env values with process.env calls and their coercion of environment variable values. This supersedes the rawEnvValues experimental flag, which is now removed.

    Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via astro:env into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.

    However, you can still access environment variables through process.env and import.meta.env directly when needed. This was the only way to use environment variables in Astro before astro:env was added in Astro 5.0, and Astro's default handling of import.meta.env includes some logic that was only needed for earlier versions of Astro.

    The experimental.staticImportMetaEnv flag updates the behavior of import.meta.env to align with Vite's handling of environment variables and for better ease of use with Astro's current implementations and features. This will become the default behavior in Astro 6.0, and this early preview is introduced as an experimental feature.

    Currently, non-public import.meta.env environment variables are replaced by a reference to process.env. Additionally, Astro may also convert the value type of your environment variables used through import.meta.env, which can prevent access to some values such as the strings "true" (which is converted to a boolean value), and "1" (which is converted to a number).

    The experimental.staticImportMetaEnv flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any import.meta.env environment variables with a process.env call, nor will it coerce values.

    To enable this feature, add the experimental flag in your Astro config and remove rawEnvValues if it was enabled:

    // astro.config.mjs
import { defineConfig } from "astro/config";

    export default defineConfig({
    

      

    • experimental: {
      • 

    • staticImportMetaEnv: true
      • 

    

      

    • rawEnvValues: false
      • 

    

      

    • }
});

Updating your project

If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:

... (truncated)

Commits

Updates astro from 5.12.8 to 5.13.2

Release notes

Sourced from astro's releases.

astro@5.13.2

Patch Changes

  • 4d16de7 Thanks @​ematipico! - Improves the detection of remote paths in the _image endpoint. Now href parameters that start with // are considered remote paths.

  • Updated dependencies [4d16de7]:

    • @​astrojs/internal-helpers@​0.7.2
    • @​astrojs/markdown-remark@​6.3.6

astro@5.13.1

Patch Changes

astro@5.13.0

Minor Changes

  • #14173 39911b8 Thanks @​florian-lefebvre! - Adds an experimental flag staticImportMetaEnv to disable the replacement of import.meta.env values with process.env calls and their coercion of environment variable values. This supersedes the rawEnvValues experimental flag, which is now removed.

    Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via astro:env into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.

    However, you can still access environment variables through process.env and import.meta.env directly when needed. This was the only way to use environment variables in Astro before astro:env was added in Astro 5.0, and Astro's default handling of import.meta.env includes some logic that was only needed for earlier versions of Astro.

    The experimental.staticImportMetaEnv flag updates the behavior of import.meta.env to align with Vite's handling of environment variables and for better ease of use with Astro's current implementations and features. This will become the default behavior in Astro 6.0, and this early preview is introduced as an experimental feature.

    Currently, non-public import.meta.env environment variables are replaced by a reference to process.env. Additionally, Astro may also convert the value type of your environment variables used through import.meta.env, which can prevent access to some values such as the strings "true" (which is converted to a boolean value), and "1" (which is converted to a number).

    The experimental.staticImportMetaEnv flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any import.meta.env environment variables with a process.env call, nor will it coerce values.

    To enable this feature, add the experimental flag in your Astro config and remove rawEnvValues if it was enabled:

    // astro.config.mjs
import { defineConfig } from "astro/config";

    export default defineConfig({
    

      

    • experimental: {
      • 

    • staticImportMetaEnv: true
      • 

    

      

    • rawEnvValues: false
      • 

    

      

    • }
});

Updating your project

If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:

// src/components/MyComponent.astro
- const enabled: boolean = import.meta.env.ENABLED;

... (truncated)

Changelog

Sourced from astro's changelog.

5.13.2

Patch Changes

  • 4d16de7 Thanks @​ematipico! - Improves the detection of remote paths in the _image endpoint. Now href parameters that start with // are considered remote paths.

  • Updated dependencies [4d16de7]:

    • @​astrojs/internal-helpers@​0.7.2
    • @​astrojs/markdown-remark@​6.3.6

5.13.1

Patch Changes

5.13.0

Minor Changes

  • #14173 39911b8 Thanks @​florian-lefebvre! - Adds an experimental flag staticImportMetaEnv to disable the replacement of import.meta.env values with process.env calls and their coercion of environment variable values. This supersedes the rawEnvValues experimental flag, which is now removed.

    Astro allows you to configure a type-safe schema for your environment variables, and converts variables imported via astro:env into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.

    However, you can still access environment variables through process.env and import.meta.env directly when needed. This was the only way to use environment variables in Astro before astro:env was added in Astro 5.0, and Astro's default handling of import.meta.env includes some logic that was only needed for earlier versions of Astro.

    The experimental.staticImportMetaEnv flag updates the behavior of import.meta.env to align with Vite's handling of environment variables and for better ease of use with Astro's current implementations and features. This will become the default behavior in Astro 6.0, and this early preview is introduced as an experimental feature.

    Currently, non-public import.meta.env environment variables are replaced by a reference to process.env. Additionally, Astro may also convert the value type of your environment variables used through import.meta.env, which can prevent access to some values such as the strings "true" (which is converted to a boolean value), and "1" (which is converted to a number).

    The experimental.staticImportMetaEnv flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any import.meta.env environment variables with a process.env call, nor will it coerce values.

    To enable this feature, add the experimental flag in your Astro config and remove rawEnvValues if it was enabled:

    // astro.config.mjs
import { defineConfig } from "astro/config";

    export default defineConfig({
    

      

    • experimental: {
      • 

    • staticImportMetaEnv: true
      • 

    

      

    • rawEnvValues: false
      • 

    

      

    • }
});

Updating your project

If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:

... (truncated)

Commits

Updates esbuild from 0.25.6 to 0.25.9

Release notes

Sourced from esbuild's releases.

v0.25.9

  • Better support building projects that use Yarn on Windows (#3131, #3663)

    With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the C: drive. The problem was as follows:

    1. Yarn in Plug'n'Play mode on Windows stores its global module cache on the C: drive
    2. Some developers put their projects on the D: drive
    3. Yarn generates relative paths that use ../.. to get from the project directory to the cache directory
    4. Windows-style paths don't support directory traversal between drives via .. (so D:\.. is just D:)
    5. I didn't have access to a Windows machine for testing this edge case

    Yarn works around this edge case by pretending Windows-style paths beginning with C:\ are actually Unix-style paths beginning with /C:/, so the ../.. path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.

  • Preserve parentheses around function expressions (#4252)

    The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.

    Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:

    // Original code
const fn0 = () => 0
const fn1 = (() => 1)
console.log(fn0, function() { return fn1() }())

    // Old output
    
const fn0 = () => 0;
    
const fn1 = () => 1;
    
console.log(fn0, function() {
    
return fn1();
    
}());
    

    // New output
    
const fn0 = () => 0;
    
const fn1 = (() => 1);
    
console.log(fn0, (function() {
    
return fn1();
    
})());

    Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.

  • Update Go from 1.23.10 to 1.23.12 (#4257, #4258)

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.

v0.25.8

  • Fix another TypeScript parsing edge case (#4248)

    This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.25.9

  • Better support building projects that use Yarn on Windows (#3131, #3663)

    With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the C: drive. The problem was as follows:

    1. Yarn in Plug'n'Play mode on Windows stores its global module cache on the C: drive
    2. Some developers put their projects on the D: drive
    3. Yarn generates relative paths that use ../.. to get from the project directory to the cache directory
    4. Windows-style paths don't support directory traversal between drives via .. (so D:\.. is just D:)
    5. I didn't have access to a Windows machine for testing this edge case

    Yarn works around this edge case by pretending Windows-style paths beginning with C:\ are actually Unix-style paths beginning with /C:/, so the ../.. path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.

  • Preserve parentheses around function expressions (#4252)

    The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.

    Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:

    // Original code
const fn0 = () => 0
const fn1 = (() => 1)
console.log(fn0, function() { return fn1() }())

    // Old output
    
const fn0 = () => 0;
    
const fn1 = () => 1;
    
console.log(fn0, function() {
    
return fn1();
    
}());
    

    // New output
    
const fn0 = () => 0;
    
const fn1 = (() => 1);
    
console.log(fn0, (function() {
    
return fn1();
    
})());

    Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.

  • Update Go from 1.23.10 to 1.23.12 (#4257, #4258)

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.

0.25.8

  • Fix another TypeScript parsing edge case (#4248)

... (truncated)

Commits

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/RayLabsHQ/gitea-mirror/pull/78 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 8/20/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/npm_and_yarn-4c1cf44590` --- ### 📝 Commits (1) - [`52507d5`](https://github.com/RayLabsHQ/gitea-mirror/commit/52507d5eb51e8261ab00d068dd7d7db2e7fe21c7) Bump the npm_and_yarn group across 2 directories with 3 updates ### 📊 Changes **3 files changed** (+426 additions, -296 deletions) <details> <summary>View changed files</summary> 📝 `package.json` (+2 -2) 📝 `www/package.json` (+1 -1) 📝 `www/pnpm-lock.yaml` (+423 -293) </details> ### 📄 Description Bumps the npm_and_yarn group with 2 updates in the / directory: [@astrojs/node](https://github.com/withastro/astro/tree/HEAD/packages/integrations/node) and [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro). Bumps the npm_and_yarn group with 1 update in the /www directory: [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro). Updates `@astrojs/node` from 9.3.3 to 9.4.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/releases"><code>@​astrojs/node</code>'s releases</a>.</em></p> <blockquote> <h2><code>@​astrojs/node</code><a href="https://github.com/9"><code>@​9</code></a>.4.1</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://github.com/withastro/astro/commit/5fc3c599cacb0172cc7d8e1202a5f2e8685d7ef2"><code>5fc3c59</code></a> Thanks <a href="https://github.com/ematipico"><code>@​ematipico</code></a>! - Fixes a routing bug in standalone mode with <code>trailingSlash</code> set to <code>&quot;always&quot;</code>.</li> </ul> <h2><code>@​astrojs/node</code><a href="https://github.com/9"><code>@​9</code></a>.4.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/14188">#14188</a> <a href="https://github.com/withastro/astro/commit/e3422aa423293d9091451d3031b7d6bfb7b46902"><code>e3422aa</code></a> Thanks <a href="https://github.com/ascorbic"><code>@​ascorbic</code></a>! - Adds support for specifying a host to load prerendered error pages</p> <p>By default, if a user defines a custom error page that is prerendered, Astro will load it from the same host as the one that the request is made to. This change allows users to specify a different host for loading prerendered error pages. This can be useful in scenarios such as where the server is running behind a reverse proxy or when prerendered pages are hosted on a different domain.</p> <p>To use this feature, set the <code>experimentalErrorPageHost</code> adapter option in your Astro configuration to the desired host URL. For example, if your server is running on localhost and served via a proxy, you can ensure the prerendered error pages are fetched via the localhost URL:</p> <pre lang="js"><code>import { defineConfig } from 'astro/config'; import node from '@astrojs/node'; export default defineConfig({ adapter: node({ // If your server is running on localhost and served via a proxy, set the host like this to ensure prerendered error pages are fetched via the localhost URL experimentalErrorPageHost: 'http://localhost:4321', }), }); </code></pre> <p>For more information on enabling and using this experimental feature, see the <a href="https://docs.astro.build/en/guides/integrations-guide/node/#experimentalerrorpagehost"><code>@astrojs/node</code> adapter docs</a>.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/blob/main/packages/integrations/node/CHANGELOG.md"><code>@​astrojs/node</code>'s changelog</a>.</em></p> <blockquote> <h2>9.4.1</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://github.com/withastro/astro/commit/5fc3c599cacb0172cc7d8e1202a5f2e8685d7ef2"><code>5fc3c59</code></a> Thanks <a href="https://github.com/ematipico"><code>@​ematipico</code></a>! - Fixes a routing bug in standalone mode with <code>trailingSlash</code> set to <code>&quot;always&quot;</code>.</li> </ul> <h2>9.4.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/14188">#14188</a> <a href="https://github.com/withastro/astro/commit/e3422aa423293d9091451d3031b7d6bfb7b46902"><code>e3422aa</code></a> Thanks <a href="https://github.com/ascorbic"><code>@​ascorbic</code></a>! - Adds support for specifying a host to load prerendered error pages</p> <p>By default, if a user defines a custom error page that is prerendered, Astro will load it from the same host as the one that the request is made to. This change allows users to specify a different host for loading prerendered error pages. This can be useful in scenarios such as where the server is running behind a reverse proxy or when prerendered pages are hosted on a different domain.</p> <p>To use this feature, set the <code>experimentalErrorPageHost</code> adapter option in your Astro configuration to the desired host URL. For example, if your server is running on localhost and served via a proxy, you can ensure the prerendered error pages are fetched via the localhost URL:</p> <pre lang="js"><code>import { defineConfig } from 'astro/config'; import node from '@astrojs/node'; export default defineConfig({ adapter: node({ // If your server is running on localhost and served via a proxy, set the host like this to ensure prerendered error pages are fetched via the localhost URL experimentalErrorPageHost: 'http://localhost:4321', }), }); </code></pre> <p>For more information on enabling and using this experimental feature, see the <a href="https://docs.astro.build/en/guides/integrations-guide/node/#experimentalerrorpagehost"><code>@astrojs/node</code> adapter docs</a>.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/withastro/astro/commit/a186848c34615dab5816df3bd8962ba16314f2b9"><code>a186848</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/integrations/node/issues/14217">#14217</a>)</li> <li><a href="https://github.com/withastro/astro/commit/d55b88a6785af74dcffe9bb3f9eef0f523df9816"><code>d55b88a</code></a> [ci] format</li> <li><a href="https://github.com/withastro/astro/commit/5fc3c599cacb0172cc7d8e1202a5f2e8685d7ef2"><code>5fc3c59</code></a> Merge commit from fork</li> <li><a href="https://github.com/withastro/astro/commit/dc9e35ccd6552063198b28f3e95a56dddcd4f1cf"><code>dc9e35c</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/integrations/node/issues/14189">#14189</a>)</li> <li><a href="https://github.com/withastro/astro/commit/56a05aaaa5ebd78808ad02a3dac66f3df09c18bb"><code>56a05aa</code></a> [ci] format</li> <li><a href="https://github.com/withastro/astro/commit/e3422aa423293d9091451d3031b7d6bfb7b46902"><code>e3422aa</code></a> feat: add support for specifying a prerendered error page host (<a href="https://github.com/withastro/astro/tree/HEAD/packages/integrations/node/issues/14188">#14188</a>)</li> <li>See full diff in <a href="https://github.com/withastro/astro/commits/@astrojs/node@9.4.1/packages/integrations/node">compare view</a></li> </ul> </details> <br /> Updates `astro` from 5.12.8 to 5.13.2 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/releases">astro's releases</a>.</em></p> <blockquote> <h2>astro@5.13.2</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820"><code>4d16de7</code></a> Thanks <a href="https://github.com/ematipico"><code>@​ematipico</code></a>! - Improves the detection of remote paths in the <code>_image</code> endpoint. Now <code>href</code> parameters that start with <code>//</code> are considered remote paths.</p> </li> <li> <p>Updated dependencies [<a href="https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820"><code>4d16de7</code></a>]:</p> <ul> <li><code>@​astrojs/internal-helpers</code><a href="https://github.com/0"><code>@​0</code></a>.7.2</li> <li><code>@​astrojs/markdown-remark</code><a href="https://github.com/6"><code>@​6</code></a>.3.6</li> </ul> </li> </ul> <h2>astro@5.13.1</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/withastro/astro/pull/14225">#14225</a> <a href="https://github.com/withastro/astro/commit/f2490aba420a8999c0e8d12b9e1e69d4e33ae29e"><code>f2490ab</code></a> Thanks <a href="https://github.com/delucis"><code>@​delucis</code></a>! - Fixes the <code>experimental.chromeDevtoolsWorkspace</code> feature.</li> </ul> <h2>astro@5.13.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/14173">#14173</a> <a href="https://github.com/withastro/astro/commit/39911b823d4617d99cc95e4b7584e9e4b7b90038"><code>39911b8</code></a> Thanks <a href="https://github.com/florian-lefebvre"><code>@​florian-lefebvre</code></a>! - Adds an experimental flag <code>staticImportMetaEnv</code> to disable the replacement of <code>import.meta.env</code> values with <code>process.env</code> calls and their coercion of environment variable values. This supersedes the <code>rawEnvValues</code> experimental flag, which is now removed.</p> <p>Astro allows you to configure a <a href="https://docs.astro.build/en/guides/environment-variables/#type-safe-environment-variables">type-safe schema for your environment variables</a>, and converts variables imported via <code>astro:env</code> into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.</p> <p>However, you can still access environment variables through <code>process.env</code> and <code>import.meta.env</code> directly when needed. This was the only way to use environment variables in Astro before <code>astro:env</code> was added in Astro 5.0, and Astro's default handling of <code>import.meta.env</code> includes some logic that was only needed for earlier versions of Astro.</p> <p>The <code>experimental.staticImportMetaEnv</code> flag updates the behavior of <code>import.meta.env</code> to align with <a href="https://vite.dev/guide/env-and-mode.html#env-variables">Vite's handling of environment variables</a> and for better ease of use with Astro's current implementations and features. <strong>This will become the default behavior in Astro 6.0</strong>, and this early preview is introduced as an experimental feature.</p> <p>Currently, non-public <code>import.meta.env</code> environment variables are replaced by a reference to <code>process.env</code>. Additionally, Astro may also convert the value type of your environment variables used through <code>import.meta.env</code>, which can prevent access to some values such as the strings <code>&quot;true&quot;</code> (which is converted to a boolean value), and <code>&quot;1&quot;</code> (which is converted to a number).</p> <p>The <code>experimental.staticImportMetaEnv</code> flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any <code>import.meta.env</code> environment variables with a <code>process.env</code> call, nor will it coerce values.</p> <p>To enable this feature, add the experimental flag in your Astro config and remove <code>rawEnvValues</code> if it was enabled:</p> <pre lang="diff"><code>// astro.config.mjs import { defineConfig } from &quot;astro/config&quot;; <p>export default defineConfig({</p> <ul> <li>experimental: {</li> <li>staticImportMetaEnv: true</li> </ul> <ul> <li>rawEnvValues: false</li> </ul> <ul> <li>} }); </code></pre></li> </ul> <h4>Updating your project</h4> <p>If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:</p> <pre lang="diff"><code>// src/components/MyComponent.astro - const enabled: boolean = import.meta.env.ENABLED; </code></pre> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md">astro's changelog</a>.</em></p> <blockquote> <h2>5.13.2</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820"><code>4d16de7</code></a> Thanks <a href="https://github.com/ematipico"><code>@​ematipico</code></a>! - Improves the detection of remote paths in the <code>_image</code> endpoint. Now <code>href</code> parameters that start with <code>//</code> are considered remote paths.</p> </li> <li> <p>Updated dependencies [<a href="https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820"><code>4d16de7</code></a>]:</p> <ul> <li><code>@​astrojs/internal-helpers</code><a href="https://github.com/0"><code>@​0</code></a>.7.2</li> <li><code>@​astrojs/markdown-remark</code><a href="https://github.com/6"><code>@​6</code></a>.3.6</li> </ul> </li> </ul> <h2>5.13.1</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/withastro/astro/pull/14225">#14225</a> <a href="https://github.com/withastro/astro/commit/f2490aba420a8999c0e8d12b9e1e69d4e33ae29e"><code>f2490ab</code></a> Thanks <a href="https://github.com/delucis"><code>@​delucis</code></a>! - Fixes the <code>experimental.chromeDevtoolsWorkspace</code> feature.</li> </ul> <h2>5.13.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/14173">#14173</a> <a href="https://github.com/withastro/astro/commit/39911b823d4617d99cc95e4b7584e9e4b7b90038"><code>39911b8</code></a> Thanks <a href="https://github.com/florian-lefebvre"><code>@​florian-lefebvre</code></a>! - Adds an experimental flag <code>staticImportMetaEnv</code> to disable the replacement of <code>import.meta.env</code> values with <code>process.env</code> calls and their coercion of environment variable values. This supersedes the <code>rawEnvValues</code> experimental flag, which is now removed.</p> <p>Astro allows you to configure a <a href="https://docs.astro.build/en/guides/environment-variables/#type-safe-environment-variables">type-safe schema for your environment variables</a>, and converts variables imported via <code>astro:env</code> into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.</p> <p>However, you can still access environment variables through <code>process.env</code> and <code>import.meta.env</code> directly when needed. This was the only way to use environment variables in Astro before <code>astro:env</code> was added in Astro 5.0, and Astro's default handling of <code>import.meta.env</code> includes some logic that was only needed for earlier versions of Astro.</p> <p>The <code>experimental.staticImportMetaEnv</code> flag updates the behavior of <code>import.meta.env</code> to align with <a href="https://vite.dev/guide/env-and-mode.html#env-variables">Vite's handling of environment variables</a> and for better ease of use with Astro's current implementations and features. <strong>This will become the default behavior in Astro 6.0</strong>, and this early preview is introduced as an experimental feature.</p> <p>Currently, non-public <code>import.meta.env</code> environment variables are replaced by a reference to <code>process.env</code>. Additionally, Astro may also convert the value type of your environment variables used through <code>import.meta.env</code>, which can prevent access to some values such as the strings <code>&quot;true&quot;</code> (which is converted to a boolean value), and <code>&quot;1&quot;</code> (which is converted to a number).</p> <p>The <code>experimental.staticImportMetaEnv</code> flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any <code>import.meta.env</code> environment variables with a <code>process.env</code> call, nor will it coerce values.</p> <p>To enable this feature, add the experimental flag in your Astro config and remove <code>rawEnvValues</code> if it was enabled:</p> <pre lang="diff"><code>// astro.config.mjs import { defineConfig } from &quot;astro/config&quot;; <p>export default defineConfig({</p> <ul> <li>experimental: {</li> <li>staticImportMetaEnv: true</li> </ul> <ul> <li>rawEnvValues: false</li> </ul> <ul> <li>} }); </code></pre></li> </ul> <h4>Updating your project</h4> <p>If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/withastro/astro/commit/92881331d1138ae146bbc4b0bfb9c675ca3f3d55"><code>9288133</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14232">#14232</a>)</li> <li><a href="https://github.com/withastro/astro/commit/1040510a0c087c644c8f75d58b28917d4f96cbf9"><code>1040510</code></a> [ci] format</li> <li><a href="https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820"><code>4d16de7</code></a> Merge commit from fork</li> <li><a href="https://github.com/withastro/astro/commit/1591bc70ce6e5636e20a1cf8eab16ec95484816b"><code>1591bc7</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14227">#14227</a>)</li> <li><a href="https://github.com/withastro/astro/commit/f2490aba420a8999c0e8d12b9e1e69d4e33ae29e"><code>f2490ab</code></a> Fix automatic Chrome DevTools workspace feature (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14225">#14225</a>)</li> <li><a href="https://github.com/withastro/astro/commit/a186848c34615dab5816df3bd8962ba16314f2b9"><code>a186848</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14217">#14217</a>)</li> <li><a href="https://github.com/withastro/astro/commit/b33780d8bf925bfddfb66105f4d46195d7fb0206"><code>b33780d</code></a> [ci] format</li> <li><a href="https://github.com/withastro/astro/commit/39911b823d4617d99cc95e4b7584e9e4b7b90038"><code>39911b8</code></a> feat: experimental static import.meta.env (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14173">#14173</a>)</li> <li><a href="https://github.com/withastro/astro/commit/41ed3ac54adf1025a38031757ee0bfaef8504092"><code>41ed3ac</code></a> feat: add automatic chrome workspace handling (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14122">#14122</a>)</li> <li><a href="https://github.com/withastro/astro/commit/806d2dc538089dd1e38623d35e75c5a6490a2494"><code>806d2dc</code></a> chore: add additional contributor to changelog (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14203">#14203</a>)</li> <li>Additional commits viewable in <a href="https://github.com/withastro/astro/commits/astro@5.13.2/packages/astro">compare view</a></li> </ul> </details> <br /> Updates `astro` from 5.12.8 to 5.13.2 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/releases">astro's releases</a>.</em></p> <blockquote> <h2>astro@5.13.2</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820"><code>4d16de7</code></a> Thanks <a href="https://github.com/ematipico"><code>@​ematipico</code></a>! - Improves the detection of remote paths in the <code>_image</code> endpoint. Now <code>href</code> parameters that start with <code>//</code> are considered remote paths.</p> </li> <li> <p>Updated dependencies [<a href="https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820"><code>4d16de7</code></a>]:</p> <ul> <li><code>@​astrojs/internal-helpers</code><a href="https://github.com/0"><code>@​0</code></a>.7.2</li> <li><code>@​astrojs/markdown-remark</code><a href="https://github.com/6"><code>@​6</code></a>.3.6</li> </ul> </li> </ul> <h2>astro@5.13.1</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/withastro/astro/pull/14225">#14225</a> <a href="https://github.com/withastro/astro/commit/f2490aba420a8999c0e8d12b9e1e69d4e33ae29e"><code>f2490ab</code></a> Thanks <a href="https://github.com/delucis"><code>@​delucis</code></a>! - Fixes the <code>experimental.chromeDevtoolsWorkspace</code> feature.</li> </ul> <h2>astro@5.13.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/14173">#14173</a> <a href="https://github.com/withastro/astro/commit/39911b823d4617d99cc95e4b7584e9e4b7b90038"><code>39911b8</code></a> Thanks <a href="https://github.com/florian-lefebvre"><code>@​florian-lefebvre</code></a>! - Adds an experimental flag <code>staticImportMetaEnv</code> to disable the replacement of <code>import.meta.env</code> values with <code>process.env</code> calls and their coercion of environment variable values. This supersedes the <code>rawEnvValues</code> experimental flag, which is now removed.</p> <p>Astro allows you to configure a <a href="https://docs.astro.build/en/guides/environment-variables/#type-safe-environment-variables">type-safe schema for your environment variables</a>, and converts variables imported via <code>astro:env</code> into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.</p> <p>However, you can still access environment variables through <code>process.env</code> and <code>import.meta.env</code> directly when needed. This was the only way to use environment variables in Astro before <code>astro:env</code> was added in Astro 5.0, and Astro's default handling of <code>import.meta.env</code> includes some logic that was only needed for earlier versions of Astro.</p> <p>The <code>experimental.staticImportMetaEnv</code> flag updates the behavior of <code>import.meta.env</code> to align with <a href="https://vite.dev/guide/env-and-mode.html#env-variables">Vite's handling of environment variables</a> and for better ease of use with Astro's current implementations and features. <strong>This will become the default behavior in Astro 6.0</strong>, and this early preview is introduced as an experimental feature.</p> <p>Currently, non-public <code>import.meta.env</code> environment variables are replaced by a reference to <code>process.env</code>. Additionally, Astro may also convert the value type of your environment variables used through <code>import.meta.env</code>, which can prevent access to some values such as the strings <code>&quot;true&quot;</code> (which is converted to a boolean value), and <code>&quot;1&quot;</code> (which is converted to a number).</p> <p>The <code>experimental.staticImportMetaEnv</code> flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any <code>import.meta.env</code> environment variables with a <code>process.env</code> call, nor will it coerce values.</p> <p>To enable this feature, add the experimental flag in your Astro config and remove <code>rawEnvValues</code> if it was enabled:</p> <pre lang="diff"><code>// astro.config.mjs import { defineConfig } from &quot;astro/config&quot;; <p>export default defineConfig({</p> <ul> <li>experimental: {</li> <li>staticImportMetaEnv: true</li> </ul> <ul> <li>rawEnvValues: false</li> </ul> <ul> <li>} }); </code></pre></li> </ul> <h4>Updating your project</h4> <p>If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:</p> <pre lang="diff"><code>// src/components/MyComponent.astro - const enabled: boolean = import.meta.env.ENABLED; </code></pre> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md">astro's changelog</a>.</em></p> <blockquote> <h2>5.13.2</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820"><code>4d16de7</code></a> Thanks <a href="https://github.com/ematipico"><code>@​ematipico</code></a>! - Improves the detection of remote paths in the <code>_image</code> endpoint. Now <code>href</code> parameters that start with <code>//</code> are considered remote paths.</p> </li> <li> <p>Updated dependencies [<a href="https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820"><code>4d16de7</code></a>]:</p> <ul> <li><code>@​astrojs/internal-helpers</code><a href="https://github.com/0"><code>@​0</code></a>.7.2</li> <li><code>@​astrojs/markdown-remark</code><a href="https://github.com/6"><code>@​6</code></a>.3.6</li> </ul> </li> </ul> <h2>5.13.1</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/withastro/astro/pull/14225">#14225</a> <a href="https://github.com/withastro/astro/commit/f2490aba420a8999c0e8d12b9e1e69d4e33ae29e"><code>f2490ab</code></a> Thanks <a href="https://github.com/delucis"><code>@​delucis</code></a>! - Fixes the <code>experimental.chromeDevtoolsWorkspace</code> feature.</li> </ul> <h2>5.13.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/14173">#14173</a> <a href="https://github.com/withastro/astro/commit/39911b823d4617d99cc95e4b7584e9e4b7b90038"><code>39911b8</code></a> Thanks <a href="https://github.com/florian-lefebvre"><code>@​florian-lefebvre</code></a>! - Adds an experimental flag <code>staticImportMetaEnv</code> to disable the replacement of <code>import.meta.env</code> values with <code>process.env</code> calls and their coercion of environment variable values. This supersedes the <code>rawEnvValues</code> experimental flag, which is now removed.</p> <p>Astro allows you to configure a <a href="https://docs.astro.build/en/guides/environment-variables/#type-safe-environment-variables">type-safe schema for your environment variables</a>, and converts variables imported via <code>astro:env</code> into the expected type. This is the recommended way to use environment variables in Astro, as it allows you to easily see and manage whether your variables are public or secret, available on the client or only on the server at build time, and the data type of your values.</p> <p>However, you can still access environment variables through <code>process.env</code> and <code>import.meta.env</code> directly when needed. This was the only way to use environment variables in Astro before <code>astro:env</code> was added in Astro 5.0, and Astro's default handling of <code>import.meta.env</code> includes some logic that was only needed for earlier versions of Astro.</p> <p>The <code>experimental.staticImportMetaEnv</code> flag updates the behavior of <code>import.meta.env</code> to align with <a href="https://vite.dev/guide/env-and-mode.html#env-variables">Vite's handling of environment variables</a> and for better ease of use with Astro's current implementations and features. <strong>This will become the default behavior in Astro 6.0</strong>, and this early preview is introduced as an experimental feature.</p> <p>Currently, non-public <code>import.meta.env</code> environment variables are replaced by a reference to <code>process.env</code>. Additionally, Astro may also convert the value type of your environment variables used through <code>import.meta.env</code>, which can prevent access to some values such as the strings <code>&quot;true&quot;</code> (which is converted to a boolean value), and <code>&quot;1&quot;</code> (which is converted to a number).</p> <p>The <code>experimental.staticImportMetaEnv</code> flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any <code>import.meta.env</code> environment variables with a <code>process.env</code> call, nor will it coerce values.</p> <p>To enable this feature, add the experimental flag in your Astro config and remove <code>rawEnvValues</code> if it was enabled:</p> <pre lang="diff"><code>// astro.config.mjs import { defineConfig } from &quot;astro/config&quot;; <p>export default defineConfig({</p> <ul> <li>experimental: {</li> <li>staticImportMetaEnv: true</li> </ul> <ul> <li>rawEnvValues: false</li> </ul> <ul> <li>} }); </code></pre></li> </ul> <h4>Updating your project</h4> <p>If you were relying on Astro's default coercion, you may need to update your project code to apply it manually:</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/withastro/astro/commit/92881331d1138ae146bbc4b0bfb9c675ca3f3d55"><code>9288133</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14232">#14232</a>)</li> <li><a href="https://github.com/withastro/astro/commit/1040510a0c087c644c8f75d58b28917d4f96cbf9"><code>1040510</code></a> [ci] format</li> <li><a href="https://github.com/withastro/astro/commit/4d16de7f95db5d1ec1ce88610d2a95e606e83820"><code>4d16de7</code></a> Merge commit from fork</li> <li><a href="https://github.com/withastro/astro/commit/1591bc70ce6e5636e20a1cf8eab16ec95484816b"><code>1591bc7</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14227">#14227</a>)</li> <li><a href="https://github.com/withastro/astro/commit/f2490aba420a8999c0e8d12b9e1e69d4e33ae29e"><code>f2490ab</code></a> Fix automatic Chrome DevTools workspace feature (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14225">#14225</a>)</li> <li><a href="https://github.com/withastro/astro/commit/a186848c34615dab5816df3bd8962ba16314f2b9"><code>a186848</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14217">#14217</a>)</li> <li><a href="https://github.com/withastro/astro/commit/b33780d8bf925bfddfb66105f4d46195d7fb0206"><code>b33780d</code></a> [ci] format</li> <li><a href="https://github.com/withastro/astro/commit/39911b823d4617d99cc95e4b7584e9e4b7b90038"><code>39911b8</code></a> feat: experimental static import.meta.env (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14173">#14173</a>)</li> <li><a href="https://github.com/withastro/astro/commit/41ed3ac54adf1025a38031757ee0bfaef8504092"><code>41ed3ac</code></a> feat: add automatic chrome workspace handling (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14122">#14122</a>)</li> <li><a href="https://github.com/withastro/astro/commit/806d2dc538089dd1e38623d35e75c5a6490a2494"><code>806d2dc</code></a> chore: add additional contributor to changelog (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/14203">#14203</a>)</li> <li>Additional commits viewable in <a href="https://github.com/withastro/astro/commits/astro@5.13.2/packages/astro">compare view</a></li> </ul> </details> <br /> Updates `esbuild` from 0.25.6 to 0.25.9 <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.9</h2> <ul> <li> <p>Better support building projects that use Yarn on Windows (<a href="https://redirect.github.com/evanw/esbuild/issues/3131">#3131</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3663">#3663</a>)</p> <p>With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the <code>C:</code> drive. The problem was as follows:</p> <ol> <li>Yarn in Plug'n'Play mode on Windows stores its global module cache on the <code>C:</code> drive</li> <li>Some developers put their projects on the <code>D:</code> drive</li> <li>Yarn generates relative paths that use <code>../..</code> to get from the project directory to the cache directory</li> <li>Windows-style paths don't support directory traversal between drives via <code>..</code> (so <code>D:\..</code> is just <code>D:</code>)</li> <li>I didn't have access to a Windows machine for testing this edge case</li> </ol> <p>Yarn works around this edge case by pretending Windows-style paths beginning with <code>C:\</code> are actually Unix-style paths beginning with <code>/C:/</code>, so the <code>../..</code> path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.</p> </li> <li> <p>Preserve parentheses around function expressions (<a href="https://redirect.github.com/evanw/esbuild/issues/4252">#4252</a>)</p> <p>The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read <a href="https://v8.dev/blog/preparser">V8's blog post about this</a> for more details.</p> <p>Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:</p> <pre lang="js"><code>// Original code const fn0 = () =&gt; 0 const fn1 = (() =&gt; 1) console.log(fn0, function() { return fn1() }()) <p>// Old output<br /> const fn0 = () =&gt; 0;<br /> const fn1 = () =&gt; 1;<br /> console.log(fn0, function() {<br /> return fn1();<br /> }());</p> <p>// New output<br /> const fn0 = () =&gt; 0;<br /> const fn1 = (() =&gt; 1);<br /> console.log(fn0, (function() {<br /> return fn1();<br /> })());<br /> </code></pre></p> <p>Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.</p> </li> <li> <p>Update Go from 1.23.10 to 1.23.12 (<a href="https://redirect.github.com/evanw/esbuild/issues/4257">#4257</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4258">#4258</a>)</p> <p>This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.</p> </li> </ul> <h2>v0.25.8</h2> <ul> <li> <p>Fix another TypeScript parsing edge case (<a href="https://redirect.github.com/evanw/esbuild/issues/4248">#4248</a>)</p> <p>This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the <code>?:</code> operator. The regression specifically involves parsing an arrow function containing a <code>#private</code> identifier inside the middle of a <code>?:</code> ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:</p> </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.9</h2> <ul> <li> <p>Better support building projects that use Yarn on Windows (<a href="https://redirect.github.com/evanw/esbuild/issues/3131">#3131</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3663">#3663</a>)</p> <p>With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the <code>C:</code> drive. The problem was as follows:</p> <ol> <li>Yarn in Plug'n'Play mode on Windows stores its global module cache on the <code>C:</code> drive</li> <li>Some developers put their projects on the <code>D:</code> drive</li> <li>Yarn generates relative paths that use <code>../..</code> to get from the project directory to the cache directory</li> <li>Windows-style paths don't support directory traversal between drives via <code>..</code> (so <code>D:\..</code> is just <code>D:</code>)</li> <li>I didn't have access to a Windows machine for testing this edge case</li> </ol> <p>Yarn works around this edge case by pretending Windows-style paths beginning with <code>C:\</code> are actually Unix-style paths beginning with <code>/C:/</code>, so the <code>../..</code> path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.</p> </li> <li> <p>Preserve parentheses around function expressions (<a href="https://redirect.github.com/evanw/esbuild/issues/4252">#4252</a>)</p> <p>The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read <a href="https://v8.dev/blog/preparser">V8's blog post about this</a> for more details.</p> <p>Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:</p> <pre lang="js"><code>// Original code const fn0 = () =&gt; 0 const fn1 = (() =&gt; 1) console.log(fn0, function() { return fn1() }()) <p>// Old output<br /> const fn0 = () =&gt; 0;<br /> const fn1 = () =&gt; 1;<br /> console.log(fn0, function() {<br /> return fn1();<br /> }());</p> <p>// New output<br /> const fn0 = () =&gt; 0;<br /> const fn1 = (() =&gt; 1);<br /> console.log(fn0, (function() {<br /> return fn1();<br /> })());<br /> </code></pre></p> <p>Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.</p> </li> <li> <p>Update Go from 1.23.10 to 1.23.12 (<a href="https://redirect.github.com/evanw/esbuild/issues/4257">#4257</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4258">#4258</a>)</p> <p>This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.</p> </li> </ul> <h2>0.25.8</h2> <ul> <li>Fix another TypeScript parsing edge case (<a href="https://redirect.github.com/evanw/esbuild/issues/4248">#4248</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/evanw/esbuild/commit/195e05c16f03a341390feef38b8ebf17d3075e14"><code>195e05c</code></a> publish 0.25.9 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/3dac33f2a2ba60387fb9aaca96b3e80b9e0512e0"><code>3dac33f</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/3131">#3131</a>, fix <a href="https://redirect.github.com/evanw/esbuild/issues/3663">#3663</a>: yarnpnp + windows + D drive</li> <li><a href="https://github.com/evanw/esbuild/commit/0f2c5c8c11dc3fa2a4e9e82df202d0b607e59de4"><code>0f2c5c8</code></a> mock fs now supports multiple volumes on windows</li> <li><a href="https://github.com/evanw/esbuild/commit/100a51e791ce714a1a90557bc9e5133fa0d38692"><code>100a51e</code></a> split out yarnpnp snapshot tests</li> <li><a href="https://github.com/evanw/esbuild/commit/13aace38bd1243e440061d1611e90a46ef55029c"><code>13aace3</code></a> remove <code>C:</code> assumption from windows snapshot tests</li> <li><a href="https://github.com/evanw/esbuild/commit/f1f413f18bce15a53fa4251f11a4747be94075e0"><code>f1f413f</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4252">#4252</a>: preserve parentheses around functions</li> <li><a href="https://github.com/evanw/esbuild/commit/1bc809190bdb68ad27fc0a6e6d385b4f635c90e2"><code>1bc8091</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4257">#4257</a>, close <a href="https://redirect.github.com/evanw/esbuild/issues/4258">#4258</a>: go 1.23.10 =&gt; 1.23.12</li> <li><a href="https://github.com/evanw/esbuild/commit/bc52135d02f794f28777c8e00db91997e0d98cab"><code>bc52135</code></a> move the go compiler version to <code>go.version</code></li> <li><a href="https://github.com/evanw/esbuild/commit/a0af5d1037c6e2509531151d153e875093f426b6"><code>a0af5d1</code></a> makefile: use <code>ESBUILD_VERSION</code> consistently</li> <li><a href="https://github.com/evanw/esbuild/commit/8c71947edbe5a158fec3a6d1cbfea1e8d5cdee70"><code>8c71947</code></a> publish 0.25.8 to npm</li> <li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.25.6...v0.25.9">compare view</a></li> </ul> </details> <br /> 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 <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/RayLabsHQ/gitea-mirror/network/alerts). </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-27 15:55:13 +03:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
fix/mirror-sync-bugs-262-263-264
v3.15.5
v3.15.4
v3.15.3
v3.15.2
v3.15.1
v3.15.0
v3.14.2
v3.14.1
v3.14.0
v3.13.4
v3.13.3
v3.13.2
v3.13.1
v3.13.0
v3.12.5
v3.12.4
v3.12.3
v3.12.2
v3.12.1
v3.12.0
v3.11.0
v3.10.1
v3.10.0
v3.9.6
v3.9.5
v3.9.4
v3.9.3
v3.9.2
v3.9.0
v3.8.11
v3.8.10
v3.8.9
v3.8.8
v3.8.7
v3.8.6
v3.8.5
v3.8.4
v3.8.3
v3.8.2
v3.8.1
v3.8.0
v3-sso
v3.7.2
v3.7.1
v3.7.0
v3.6.0
v3.5.4
v3.5.3
v3.5.2
v3.5.1
v3.5.0
v3.4.0
v3.3.0
v3.2.6
v3.2.5
v3.2.4
v3.2.3
v3.2.2
v3.2.1
v3.2.0
v3.1.1
v3.1.0
v3.0.1
v3.0.0
v2.22.0
v2.21.0
v2.20.1
v2.20.0
v2.18.0
v2.17.0
v2.16.3
v2.16.2
v2.16.1
v2.16.0
v2.15.0
v2.14.0
v2.13.2
v2.13.1
v2.13.0
v2.12.0
v2.11.2
v2.11.1
v2.11.0
v2.10.0
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.0
v2.7.0
v2.6.0
v2.5.4
v2.5.3
v2.5.2
v2.5.1
v2.5.0
v2.1.0
v2.0.0
v1.0.0
Labels
Clear labels   
bug

   
documentation

   
enhancement

   
help wanted

   
pull-request

Mirrored from GitHub Pull Request

  
question
No labels
bug
documentation
enhancement
help wanted
pull-request
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/gitea-mirror#123
No description provided.