chore(deps): bump the npm_and_yarn group with 3 updates

[dependabot]

Bumps the npm_and_yarn group with 3 updates: esbuild, @astrojs/mdx and astro.

Updates esbuild from 0.21.5 to 0.25.0

Release notes

Sourced from esbuild's releases.

v0.25.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.24.0 or ~0.24.0. See npm's documentation about semver for more information.

• Restrict access to esbuild's development server (GHSA-67mh-4wv8-2f99)

  This change addresses esbuild's first security vulnerability report. Previously esbuild set the Access-Control-Allow-Origin header to * to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in the report.

  Starting with this release, CORS will now be disabled, and requests will now be denied if the host does not match the one provided to --serve=. The default host is 0.0.0.0, which refers to all of the IP addresses that represent the local machine (e.g. both 127.0.0.1 and 192.168.0.1). If you want to customize anything about esbuild's development server, you can put a proxy in front of esbuild and modify the incoming and/or outgoing requests.

  In addition, the serve() API call has been changed to return an array of hosts instead of a single host string. This makes it possible to determine all of the hosts that esbuild's development server will accept.

  Thanks to @​sapphi-red for reporting this issue.

• Delete output files when a build fails in watch mode (#3643)

  It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.

• Fix correctness issues with the CSS nesting transform (#3620, #3877, #3933, #3997, #4005, #4037, #4038)

  This release fixes the following problems:

  • Naive expansion of CSS nesting can result in an exponential blow-up of generated CSS if each nesting level has multiple selectors. Previously esbuild sometimes collapsed individual nesting levels using :is() to limit expansion. However, this collapsing wasn't correct in some cases, so it has been removed to fix correctness issues.

    /* Original code */
    .parent {
      > .a,
      > .b1 > .b2 {
        color: red;
      }
    }
    /* Old output (with --supported:nesting=false) */
    .parent > :is(.a, .b1 > .b2) {
    color: red;
    }
    /* New output (with --supported:nesting=false) */
    .parent > .a,
    .parent > .b1 > .b2 {
    color: red;
    }

    Thanks to @​tim-we for working on a fix.

  • The & CSS nesting selector can be repeated multiple times to increase CSS specificity. Previously esbuild ignored this possibility and incorrectly considered && to have the same specificity as &. With this release, this should now work correctly:

    /* Original code (color should be red) */

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2024

This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).

0.24.2

• Fix regression with --define and import.meta (#4010, #4012, #4013)

  The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

  This fix was contributed by @​sapphi-red.

0.24.1

• Allow es2024 as a target in tsconfig.json (#4004)

  TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

  {
    "compilerOptions": {
      "target": "ES2024"
    }
  }

  As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

  This fix was contributed by @​billyjanitsch.

• Allow automatic semicolon insertion after get/set

  This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

  class Foo {
    get
    *x() {}
    set
    *y() {}
  }

  The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

• Allow quoted property names in --define and --pure (#4008)

  The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

... (truncated)

Commits

• e9174d6 publish 0.25.0 to npm
• c27dbeb fix hosts in plugin-tests.js
• 6794f60 fix hosts in node-unref-tests.js
• de85afd Merge commit from fork
• da1de1b fix #4065: bitwise operators can return bigints
• f4e9d19 switch case liveness: default is always last
• 7aa47c3 fix #4028: minify live/dead switch cases better
• 22ecd30 minify: more constant folding for strict equality
• 4cdf03c fix #4053: reordering of .tsx in node_modules
• dc71977 fix #3692: 0 now picks a random ephemeral port
• Additional commits viewable in compare view

Updates @astrojs/mdx from 3.1.9 to 4.1.0

Release notes

Sourced from @​astrojs/mdx's releases.

@​astrojs/mdx@​4.1.0

Minor Changes

• #13254 1e11f5e Thanks @​p0lyw0lf! - Adds the ability to process and optimize remote images in Markdown syntax in MDX files.

  Previously, Astro only allowed local images to be optimized when included using ![]() syntax. Astro's image service could only display remote images without any processing.

  Now, Astro's image service can also optimize remote images written in standard Markdown syntax. This allows you to enjoy the benefits of Astro's image processing when your images are stored externally, for example in a CMS or digital asset manager.

  No additional configuration is required to use this feature! Any existing remote images written in Markdown will now automatically be optimized. To opt-out of this processing, write your images in Markdown using the JSX <img/> tag instead. Note that images located in your public/ folder are still never processed.

Patch Changes

• Updated dependencies [1e11f5e]:
  • @​astrojs/markdown-remark@​6.2.0

@​astrojs/mdx@​4.0.8

Patch Changes

• Updated dependencies [db252e0]:
  • @​astrojs/markdown-remark@​6.1.0

@​astrojs/mdx@​4.0.7

Patch Changes

• #13011 cf30880 Thanks @​ascorbic! - Upgrades Vite

@​astrojs/mdx@​4.0.6

Patch Changes

• Updated dependencies [3d89e62]:
  • @​astrojs/markdown-remark@​6.0.2

@​astrojs/mdx@​4.0.5

Patch Changes

• #12959 3a267f3 Thanks @​bluwy! - Reverts withastro/astro@9a3b48c which caused a regression for rendering inline MDX components and MDX files from content collections

@​astrojs/mdx@​4.0.4

Patch Changes

• #12921 aeb7e1a Thanks @​ascorbic! - Fixes a bug that caused Image component to be imported on MDX pages that did not include images

• #12913 9a3b48c Thanks @​bluwy! - Makes internal check() function a no-op to allow faster component renders and prevent React 19 component warnings

@​astrojs/mdx@​4.0.3

Patch Changes

• #12799 739dbfb Thanks @​ascorbic! - Upgrades Vite to pin esbuild

Changelog

Sourced from @​astrojs/mdx's changelog.

4.1.0

Minor Changes

• #13254 1e11f5e Thanks @​p0lyw0lf! - Adds the ability to process and optimize remote images in Markdown syntax in MDX files.

  Previously, Astro only allowed local images to be optimized when included using ![]() syntax. Astro's image service could only display remote images without any processing.

  Now, Astro's image service can also optimize remote images written in standard Markdown syntax. This allows you to enjoy the benefits of Astro's image processing when your images are stored externally, for example in a CMS or digital asset manager.

  No additional configuration is required to use this feature! Any existing remote images written in Markdown will now automatically be optimized. To opt-out of this processing, write your images in Markdown using the JSX <img/> tag instead. Note that images located in your public/ folder are still never processed.

Patch Changes

• Updated dependencies [1e11f5e]:
  • @​astrojs/markdown-remark@​6.2.0

4.0.8

Patch Changes

• Updated dependencies [db252e0]:
  • @​astrojs/markdown-remark@​6.1.0

4.0.7

Patch Changes

• #13011 cf30880 Thanks @​ascorbic! - Upgrades Vite

4.0.6

Patch Changes

• Updated dependencies [3d89e62]:
  • @​astrojs/markdown-remark@​6.0.2

4.0.5

Patch Changes

• #12959 3a267f3 Thanks @​bluwy! - Reverts withastro/astro@9a3b48c which caused a regression for rendering inline MDX components and MDX files from content collections

4.0.4

Patch Changes

• #12921 aeb7e1a Thanks @​ascorbic! - Fixes a bug that caused Image component to be imported on MDX pages that did not include images

• #12913 9a3b48c Thanks @​bluwy! - Makes internal check() function a no-op to allow faster component renders and prevent React 19 component warnings

... (truncated)

Commits

• 9aa5ac1 [ci] release (#13318)
• 1e11f5e feat: Pass remote Markdown images through image service (#13254)
• cbd056c fix(deps): update all non-major dependencies (#13074)
• f6b7839 [ci] release (#13086)
• 61ef2d9 chore: upgrade Vite and update tests (#13076)
• 0a0b197 [ci] release (#12991)
• 3357ff6 fix(deps): update all non-major dependencies (#13008)
• cf30880 fix: upgrade Vite and update tests (#13011)
• 0968069 [ci] release (#12978)
• 7a0855b fix(deps): update all non-major dependencies (#12579)
• Additional commits viewable in compare view

Updates astro from 4.16.18 to 5.4.2

Release notes

Sourced from astro's releases.

astro@5.4.2

Patch Changes

• #12985 84e94cc Thanks @​matthewp! - Prevent re-executing scripts in client router

• #13349 50e2e0b Thanks @​ascorbic! - Correctly escapes attributes in Markdown images

• #13262 0025df3 Thanks @​ematipico! - Refactor Astro Actions to not use a middleware. Doing so should avoid unexpected issues when using the Astro middleware at the edge.

astro@5.4.1

Patch Changes

• #13336 8f632ef Thanks @​ematipico! - Fixes a regression where some asset utilities were move across monorepo, and not re-exported anymore.

• #13320 b5dabe9 Thanks @{! - Adds support for typing experimental session data

  You can add optional types to your session data by creating a src/env.d.ts file in your project that extends the global App.SessionData interface. For example:

  declare namespace App {
    interface SessionData {
    id: string;
    email: string;
  };
  lastLogin: Date;
  
  }
  }

  Any keys not defined in this interface will be treated as any.

  Then when you access Astro.session in your components, any defined keys will be typed correctly:

  ---
  const user = await Astro.session.get('user');
  //    ^? const: user: { id: string; email: string; } | undefined
  const something = await Astro.session.get('something');
  //    ^? const: something: any
  Astro.session.set('user', 1);
  //    ^? Argument of type 'number' is not assignable to parameter of type '{ id: string; email: string; }'.

  See the experimental session docs for more information.

• #13330 5e7646e Thanks @​ematipico! - Fixes an issue with the conditional rendering of scripts.

... (truncated)

Changelog

Sourced from astro's changelog.

5.4.2

Patch Changes

• #12985 84e94cc Thanks @​matthewp! - Prevent re-executing scripts in client router

• #13349 50e2e0b Thanks @​ascorbic! - Correctly escapes attributes in Markdown images

• #13262 0025df3 Thanks @​ematipico! - Refactor Astro Actions to not use a middleware. Doing so should avoid unexpected issues when using the Astro middleware at the edge.

5.4.1

Patch Changes

• #13336 8f632ef Thanks @​ematipico! - Fixes a regression where some asset utilities were move across monorepo, and not re-exported anymore.

• #13320 b5dabe9 Thanks @{! - Adds support for typing experimental session data

  You can add optional types to your session data by creating a src/env.d.ts file in your project that extends the global App.SessionData interface. For example:

  declare namespace App {
    interface SessionData {
    id: string;
    email: string;
  };
  lastLogin: Date;
  
  }
  }

  Any keys not defined in this interface will be treated as any.

  Then when you access Astro.session in your components, any defined keys will be typed correctly:

  ---
  const user = await Astro.session.get('user');
  //    ^? const: user: { id: string; email: string; } | undefined
  const something = await Astro.session.get('something');
  //    ^? const: something: any
  Astro.session.set('user', 1);
  //    ^? Argument of type 'number' is not assignable to parameter of type '{ id: string; email: string; }'.

  See the experimental session docs for more information.

... (truncated)

Commits

• c67a351 [ci] release (#13350)
• f61d442 [ci] format
• 0025df3 refactor(core): move actions inside core (#13262)
• fe8cacd [ci] format
• 16d6d41 fix(deps): update all non-major dependencies (#13346)
• 55ef4f5 [ci] format
• 84e94cc Prevent rerunning scripts already ran in router (#12985)
• 21c233c [ci] format
• 50e2e0b fix: escape img attributes in Markdown (#13349)
• 8483502 [ci] release (#13337)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[netlify]

❌ Deploy Preview for astro-vanilla failed.

Name	Link
🔨 Latest commit	72b20da
🔍 Latest deploy log	https://app.netlify.com/sites/astro-vanilla/deploys/67eb6c58886531000987585c