Bump esbuild, @astrojs/cloudflare and astro

[dependabot]

Bumps esbuild to 0.25.2 and updates ancestor dependencies esbuild, @astrojs/cloudflare and astro. These dependencies need to be updated together.

Updates esbuild from 0.21.5 to 0.25.2

Release notes

Sourced from esbuild's releases.

v0.25.2

• Support flags in regular expressions for the API (#4121)

  The JavaScript plugin API for esbuild takes JavaScript regular expression objects for the filter option. Internally these are translated into Go regular expressions. However, this translation previously ignored the flags property of the regular expression. With this release, esbuild will now translate JavaScript regular expression flags into Go regular expression flags. Specifically the JavaScript regular expression /\.[jt]sx?$/i is turned into the Go regular expression `(?i)\.[jt]sx?$` internally inside of esbuild's API. This should make it possible to use JavaScript regular expressions with the i flag. Note that JavaScript and Go don't support all of the same regular expression features, so this mapping is only approximate.

• Fix node-specific annotations for string literal export names (#4100)

  When node instantiates a CommonJS module, it scans the AST to look for names to expose via ESM named exports. This is a heuristic that looks for certain patterns such as exports.NAME = ... or module.exports = { ... }. This behavior is used by esbuild to "annotate" CommonJS code that was converted from ESM with the original ESM export names. For example, when converting the file export let foo, bar from ESM to CommonJS, esbuild appends this to the end of the file:

  // Annotate the CommonJS export names for ESM import in node:
  0 && (module.exports = {
    bar,
    foo
  });

  However, this feature previously didn't work correctly for export names that are not valid identifiers, which can be constructed using string literal export names. The generated code contained a syntax error. That problem is fixed in this release:

  // Original code
  let foo
  export { foo as "foo!" }
  // Old output (with --format=cjs --platform=node)
  ...
  0 && (module.exports = {
  "foo!"
  });
  // New output (with --format=cjs --platform=node)
  ...
  0 && (module.exports = {
  "foo!": null
  });

• Basic support for index source maps (#3439, #4109)

  The source map specification has an optional mode called index source maps that makes it easier for tools to create an aggregate JavaScript file by concatenating many smaller JavaScript files with source maps, and then generate an aggregate source map by simply providing the original source maps along with some offset information. My understanding is that this is rarely used in practice. I'm only aware of two uses of it in the wild: ClojureScript and Turbopack.

  This release provides basic support for indexed source maps. However, the implementation has not been tested on a real app (just on very simple test input). If you are using index source maps in a real app, please try this out and report back if anything isn't working for you.

  Note that this is also not a complete implementation. For example, index source maps technically allows nesting source maps to an arbitrary depth, while esbuild's implementation in this release only supports a single level of nesting. It's unclear whether supporting more than one level of nesting is important or not given the lack of available test cases.

  This feature was contributed by @​clyfish.

v0.25.1

• Fix incorrect paths in inline source maps (#4070, #4075, #4105)

... (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

• 4475787 publish 0.25.2 to npm
• 8f56771 fix #4121: map js regexp flags to go regexp flags
• 36b458d follow-up to #4109
• 8b8437c feat: support index source map (#4109)
• 75286c1 unit test for absolute windows paths in source map
• bcc77fb fix #4100: invalid identifiers in node annotation
• 37cb6a2 fix a warning from npm publish
• 6bfc1c1 publish 0.25.1 to npm
• f9b3952 fix #4078: prepend namespaces to source map paths
• ccf3dd7 add "contributed by" in changelog
• Additional commits viewable in compare view

Updates @astrojs/cloudflare from 12.1.0 to 12.4.0

Release notes

Sourced from @​astrojs/cloudflare's releases.

@​astrojs/cloudflare@​12.4.0

Minor Changes

• #13514 a9aafec Thanks @​ascorbic! - Automatically configures Cloudflare KV storage when experimental sessions are enabled

  If the experimental.session flag is enabled when using the Cloudflare adapter, Astro will automatically configure the session storage using the Cloudflare KV driver. You can still manually configure the session storage if you need to use a different driver or want to customize the session storage configuration. If you want to use sessions, you will need to create the KV namespace and declare it in your wrangler config. You can do this using the Wrangler CLI:

  npx wrangler kv namespace create SESSION

  This will log the id of the created namespace. You can then add it to your wrangler.json/wrangler.toml file like this:

  // wrangler.json
  {
    "kv_namespaces": [
      {
        "binding": "SESSION",
        "id": "<your kv namespace id here>",
      },
    ],
  }

  By default it uses the binding name SESSION, but if you want to use a different binding name you can do so by passing the sessionKVBindingName option to the adapter. For example:

  import { defineConfig } from 'astro/config';
  import cloudflare from '@astrojs/cloudflare';
  export default defineConfig({
    output: 'server',
    site: `http://example.com`,
    adapter: cloudflare({
      platformProxy: {
        enabled: true,
      },
      sessionKVBindingName: 'MY_SESSION',
    }),
    experimental: {
      session: true,
    },
  });

  See the Cloudflare KV docs for more details on setting up KV namespaces.

  See the experimental session docs for more information on configuring session storage.

Patch Changes

... (truncated)

Changelog

Sourced from @​astrojs/cloudflare's changelog.

12.4.0

Minor Changes

• #13514 a9aafec Thanks @​ascorbic! - Automatically configures Cloudflare KV storage when experimental sessions are enabled

  If the experimental.session flag is enabled when using the Cloudflare adapter, Astro will automatically configure the session storage using the Cloudflare KV driver. You can still manually configure the session storage if you need to use a different driver or want to customize the session storage configuration. If you want to use sessions, you will need to create the KV namespace and declare it in your wrangler config. You can do this using the Wrangler CLI:

  npx wrangler kv namespace create SESSION

  This will log the id of the created namespace. You can then add it to your wrangler.json/wrangler.toml file like this:

  // wrangler.json
  {
    "kv_namespaces": [
      {
        "binding": "SESSION",
        "id": "<your kv namespace id here>",
      },
    ],
  }

  By default it uses the binding name SESSION, but if you want to use a different binding name you can do so by passing the sessionKVBindingName option to the adapter. For example:

  import { defineConfig } from 'astro/config';
  import cloudflare from '@astrojs/cloudflare';
  export default defineConfig({
    output: 'server',
    site: `http://example.com`,
    adapter: cloudflare({
      platformProxy: {
        enabled: true,
      },
      sessionKVBindingName: 'MY_SESSION',
    }),
    experimental: {
      session: true,
    },
  });

  See the Cloudflare KV docs for more details on setting up KV namespaces.

  See the experimental session docs for more information on configuring session storage.

... (truncated)

Commits

• See full diff in compare view

Updates astro from 5.1.3 to 5.5.6

Release notes

Sourced from astro's releases.

astro@5.5.6

Patch Changes

• #13429 06de673 Thanks @​ematipico! - The ActionAPIContext.rewrite method is deprecated and will be removed in a future major version of Astro

• #13524 82cd583 Thanks @​ematipico! - Fixes a bug where the functions Astro.preferredLocale and Astro.preferredLocaleList would return the incorrect locales when the Astro configuration specifies a list of codes. Before, the functions would return the path, instead now the functions return a list built from codes.

• #13526 ff9d69e Thanks @​jsparkdev! - update vite to the latest version

astro@5.5.5

Patch Changes

• #13510 5b14d33 Thanks @​florian-lefebvre! - Fixes a case where astro:env secrets used in actions would not be available

• #13485 018fbe9 Thanks @​ascorbic! - Fixes a bug that caused cookies to ignore custom decode function if has() had been called before

• #13505 a98ae5b Thanks @​ematipico! - Updates the dependency vite to the latest.

• #13483 fc2dcb8 Thanks @​ematipico! - Fixes a bug where an Astro adapter couldn't call the middleware when there isn't a route that matches the incoming request.

astro@5.5.4

Patch Changes

• #13457 968e713 Thanks @​ascorbic! - Sets correct response status text for custom error pages

• #13447 d80ba2b Thanks @​ematipico! - Fixes an issue where site was added to the generated redirects.

• #13481 e9e9245 Thanks @​martrapp! - Makes server island work with the client router again.

• #13484 8b5e4dc Thanks @​ascorbic! - Display useful errors when config loading fails because of Node addons being disabled on Stackblitz

astro@5.5.3

Patch Changes

• #13437 013fa87 Thanks @​Vardhaman619! - Handle server.allowedHosts when the value is true without attempting to push it into an array.

• #13324 ea74336 Thanks @​ematipico! - Upgrade to shiki v3

• #13372 7783dbf Thanks @​ascorbic! - Fixes a bug that caused some very large data stores to save incomplete data.

• #13358 8c21663 Thanks @​ematipico! - Adds a new function called insertPageRoute to the Astro Container API.

  The new function is useful when testing routes that, for some business logic, use Astro.rewrite.

  For example, if you have a route /blog/post and for some business decision there's a rewrite to /generic-error, the container API implementation will look like this:

  import Post from '../src/pages/Post.astro';

... (truncated)

Changelog

Sourced from astro's changelog.

5.5.6

Patch Changes

• #13429 06de673 Thanks @​ematipico! - The ActionAPIContext.rewrite method is deprecated and will be removed in a future major version of Astro

• #13524 82cd583 Thanks @​ematipico! - Fixes a bug where the functions Astro.preferredLocale and Astro.preferredLocaleList would return the incorrect locales when the Astro configuration specifies a list of codes. Before, the functions would return the path, instead now the functions return a list built from codes.

• #13526 ff9d69e Thanks @​jsparkdev! - update vite to the latest version

5.5.5

Patch Changes

• #13510 5b14d33 Thanks @​florian-lefebvre! - Fixes a case where astro:env secrets used in actions would not be available

• #13485 018fbe9 Thanks @​ascorbic! - Fixes a bug that caused cookies to ignore custom decode function if has() had been called before

• #13505 a98ae5b Thanks @​ematipico! - Updates the dependency vite to the latest.

• #13483 fc2dcb8 Thanks @​ematipico! - Fixes a bug where an Astro adapter couldn't call the middleware when there isn't a route that matches the incoming request.

5.5.4

Patch Changes

• #13457 968e713 Thanks @​ascorbic! - Sets correct response status text for custom error pages

• #13447 d80ba2b Thanks @​ematipico! - Fixes an issue where site was added to the generated redirects.

• #13481 e9e9245 Thanks @​martrapp! - Makes server island work with the client router again.

• #13484 8b5e4dc Thanks @​ascorbic! - Display useful errors when config loading fails because of Node addons being disabled on Stackblitz

5.5.3

Patch Changes

• #13437 013fa87 Thanks @​Vardhaman619! - Handle server.allowedHosts when the value is true without attempting to push it into an array.

• #13324 ea74336 Thanks @​ematipico! - Upgrade to shiki v3

• #13372 7783dbf Thanks @​ascorbic! - Fixes a bug that caused some very large data stores to save incomplete data.

• #13358 8c21663 Thanks @​ematipico! - Adds a new function called insertPageRoute to the Astro Container API.

  The new function is useful when testing routes that, for some business logic, use Astro.rewrite.

... (truncated)

Commits

• ddc98eb [ci] release (#13513)
• ff9d69e fix: update vite to latest version (#13526)
• b8645c1 [ci] format
• 82cd583 fix(i18n): return value from preferredLocale (#13524)
• 32499c0 chore(tailwind): delete integration (#13511)
• a5061d6 fix(deps): update astro dependencies (#13498)
• 7185491 [ci] format
• 06de673 refactor(actions): use Omit to avoid leaking types to shared context (#13429)
• b33cc17 [ci] release (#13504)
• 3488324 [ci] format
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Summary by Sourcery

Update dependencies for Astro, Cloudflare adapter, and related packages to their latest versions

Enhancements:

• Upgrade esbuild to version 0.25.2 with improved regular expression flag handling and source map support
• Update Cloudflare adapter to version 12.4.0 with automatic KV storage configuration for experimental sessions
• Upgrade Astro to version 5.5.6 with various bug fixes and improvements

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the esbuild, @astrojs/cloudflare, and astro dependencies to their latest versions. The dependencies were updated in package.json and package-lock.json.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Updated the esbuild dependency to version 0.25.2.	Updated esbuild from version 0.21.5 to 0.25.2.	package.json package-lock.json
Updated the @astrojs/cloudflare dependency to version 12.4.0.	Updated @astrojs/cloudflare from version 12.1.0 to 12.4.0.	package.json package-lock.json
Updated the astro dependency to version 5.5.6.	Updated astro from version 5.1.3 to 5.5.6.	package.json package-lock.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!