fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/partytown (source)	2.1.2 -> 2.1.3
@astrojs/react (source)	3.6.2 -> 3.6.3
@astrojs/rss (source)	4.0.9 -> 4.0.11
@babel/core (source)	7.25.9 -> 7.26.0
@babel/preset-env (source)	7.25.9 -> 7.26.0
@babel/preset-typescript (source)	7.25.9 -> 7.26.0
@changesets/cli (source)	2.27.9 -> 2.27.11
@std-uritemplate/std-uritemplate	2.0.0 -> 2.0.1
@types/node (source)	20.16.15 -> 20.17.11
@types/react (source)	18.3.12 -> 18.3.18
@types/react-dom (source)	18.3.1 -> 18.3.5
astro (source)	4.16.7 -> 4.16.18
debug	4.3.7 -> 4.4.0
esbuild	0.24.0 -> 0.24.2
husky	9.1.6 -> 9.1.7
lint-staged	15.2.10 -> 15.3.0
pnpm (source)	9.12.2 -> 9.15.2
prettier (source)	3.3.3 -> 3.4.2
turbo (source)	2.2.3 -> 2.3.3
typescript (source)	5.6.3 -> 5.7.2
vite (source)	5.4.10 -> 5.4.11
zod (source)	3.23.8 -> 3.24.1

---

Release Notes

withastro/astro (@​astrojs/partytown)

v2.1.3

Compare Source

Patch Changes

• #​12822 1fab2f2 Thanks @​stdavis! - Updates the partytown dependency to the new npm org name and latest version.

withastro/astro (@​astrojs/react)

v3.6.3

Compare Source

Patch Changes

• #​12481 8a46e80 Thanks @​marbrex! - Resolve vite peer dependency problem for strict package managers like Yarn in PnP mode.

withastro/astro (@​astrojs/rss)

v4.0.11

Compare Source

Patch Changes

• #​12829 ebe2aa9 Thanks @​SapphicMoe! - Revert incorrect Content-Type header applied for RSS XML file

v4.0.10

Compare Source

Patch Changes

• #​12644 5b9b618 Thanks @​kunyan! - Sends the standard RSS content type response header, with UTF-8 charset

babel/babel (@​babel/core)

v7.26.0

Compare Source

babel/babel (@​babel/preset-env)

v7.26.0

Compare Source

🚀 New Feature

• babel-core, babel-generator, babel-parser, babel-plugin-syntax-import-assertions, babel-plugin-syntax-import-attributes, babel-preset-env, babel-standalone, babel-types
  • #​16850 Enable import attributes parsing by default (@​nicolo-ribaudo)
• babel-core
  • #​16862 feat: support async plugin's pre/post (@​timofei-iatsenko)
• babel-compat-data, babel-plugin-proposal-regexp-modifiers, babel-plugin-transform-regexp-modifiers, babel-preset-env, babel-standalone
  • #​16692 Add transform-regexp-modifiers to preset-env (@​JLHwung)
• babel-parser
  • #​16849 feat: add startIndex parser option (@​DylanPiercey)
• babel-generator, babel-parser, babel-plugin-syntax-flow
  • #​16841 Always enable parsing of Flow enums (@​nicolo-ribaudo)
• babel-helpers, babel-preset-typescript, babel-runtime-corejs3
  • #​16794 Support import() in rewriteImportExtensions (@​liuxingbaoyu)
• babel-generator, babel-parser
  • #​16708 Add experimental format-preserving mode to @babel/generator (@​nicolo-ribaudo)

🐛 Bug Fix

• babel-core
  • #​16928 Workaround Node.js bug for parallel loading of TLA modules (@​nicolo-ribaudo)
  • #​16926 Fix loading of modules with TLA in Node.js 23 (@​nicolo-ribaudo)

💅 Polish

• babel-plugin-proposal-json-modules, babel-plugin-transform-json-modules, babel-standalone
  • #​16924 Rename proposal-json-modules to transform-json-modules (@​nicolo-ribaudo)

🏠 Internal

• babel-code-frame, babel-highlight
  • #​16896 Inline @babel/highlight in @babel/code-frame (@​nicolo-ribaudo)
• babel-generator, babel-parser, babel-types
  • #​16732 Add kind to TSModuleDeclaration (@​liuxingbaoyu)

🏃‍♀️ Performance

• babel-helper-module-transforms, babel-plugin-transform-modules-commonjs
  • #​16882 perf: Improve module transforms (@​liuxingbaoyu)

changesets/changesets (@​changesets/cli)

v2.27.11

Compare Source

Patch Changes

• Updated dependencies [f0270f6]:
  • @​changesets/config@​3.0.5
  • @​changesets/apply-release-plan@​7.0.7
  • @​changesets/get-release-plan@​4.0.6

v2.27.10

Compare Source

std-uritemplate/std-uritemplate (@​std-uritemplate/std-uritemplate)

v2.0.1

Compare Source

withastro/astro (astro)

v4.16.18

Compare Source

Patch Changes

• #​12757 d0aaac3 Thanks @​matthewp! - Remove all assets created from the server build

• #​12757 d0aaac3 Thanks @​matthewp! - Clean server sourcemaps from static output

v4.16.17

Compare Source

Patch Changes

• #​12632 e7d14c3 Thanks @​ematipico! - Fixes an issue where the checkOrigin feature wasn't correctly checking the content-type header

v4.16.16

Compare Source

Patch Changes

• #​12542 65e50eb Thanks @​kadykov! - Fix JPEG image size determination

• #​12525 cf0d8b0 Thanks @​ematipico! - Fixes an issue where with i18n enabled, Astro couldn't render the 404.astro component for non-existent routes.

v4.16.15

Compare Source

Patch Changes

• #​12498 b140a3f Thanks @​ematipico! - Fixes a regression where Astro was trying to access Request.headers

v4.16.14

Compare Source

Patch Changes

• #​12480 c3b7e7c Thanks @​matthewp! - Removes the default throw behavior in astro:env

• #​12444 28dd3ce Thanks @​ematipico! - Fixes an issue where a server island hydration script might fail case the island ID misses from the DOM.

• #​12476 80a9a52 Thanks @​florian-lefebvre! - Fixes a case where the Content Layer glob() loader would not update when renaming or deleting an entry

• #​12418 25baa4e Thanks @​oliverlynch! - Fix cached image redownloading if it is the first asset

• #​12477 46f6b38 Thanks @​ematipico! - Fixes an issue where the SSR build was emitting the dist/server/entry.mjs file with an incorrect import at the top of the file/

• #​12365 a23985b Thanks @​apatel369! - Fixes an issue where Astro.currentLocale was not correctly returning the locale for 404 and 500 pages.

v4.16.13

Compare Source

Patch Changes

• #​12436 453ec6b Thanks @​martrapp! - Fixes a potential null access in the clientside router

• #​12392 0462219 Thanks @​apatel369! - Fixes an issue where scripts were not correctly injected during the build. The issue was triggered when there were injected routes with the same entrypoint and different pattern

v4.16.12

Compare Source

Patch Changes

• #​12420 acac0af Thanks @​ematipico! - Fixes an issue where the dev server returns a 404 status code when a user middleware returns a valid Response.

v4.16.11

Compare Source

Patch Changes

• #​12305 f5f7109 Thanks @​florian-lefebvre! - Fixes a case where the error overlay would not escape the message

• #​12402 823e73b Thanks @​ematipico! - Fixes a case where Astro allowed to call an action without using Astro.callAction. This is now invalid, and Astro will show a proper error.

v4.16.10

Compare Source

Patch Changes

• #​12311 bf2723e Thanks @​dinesh-58! - Adds checked to the list of boolean attributes.

• #​12363 222f718 Thanks @​Fryuni! - Fixes code generated by astro add command when adding a version of an integration other than the default latest.

• #​12368 493fe43 Thanks @​bluwy! - Improves error logs when executing commands

• #​12355 c4726d7 Thanks @​apatel369! - Improves error reporting for invalid frontmatter in MDX files during the astro build command. The error message now includes the file path where the frontmatter parsing failed.

v4.16.9

Compare Source

Patch Changes

• #​12333 836cd91 Thanks @​imattacus! - Destroy the server response stream if async error is thrown

• #​12358 7680349 Thanks @​spacedawwwg! - Honors inlineAstroConfig parameter in getViteConfig when creating a logger

• #​12353 35795a1 Thanks @​hippotastic! - Fixes an issue in dev server watch file handling that could cause multiple restarts for a single file change.

• #​12351 5751488 Thanks @​florian-lefebvre! - Reverts a change made in 4.16.6 that prevented usage of astro:env secrets inside middleware in SSR

• #​12346 20e5a84 Thanks @​bluwy! - Fixes sourcemap generation when prefetch is enabled

• #​12349 1fc83d3 Thanks @​norskeld! - Fixes the getImage options type so it properly extends ImageTransform

v4.16.8

Compare Source

Patch Changes

• #​12338 9ca89b3 Thanks @​situ2001! - Resets NODE_ENV to ensure install command run in dev mode

• #​12286 9d6bcdb Thanks @​florian-lefebvre! - Fixes a case where a warning for experimental astro:env support would be shown when using an adapter but not actually using astro:env

• #​12342 ffc836b Thanks @​liruifengv! - Fixes a typo in the command name of the CLI

• #​12301 0cfc69d Thanks @​apatel369! - Fixes an issue with action handler context by passing the correct context (ActionAPIContext).

• #​12312 5642ef9 Thanks @​koyopro! - Fixes an issue where using getViteConfig() returns incorrect and duplicate configuration

• #​12245 1d4f6a4 Thanks @​bmenant! - Add components property to MDXInstance type definition (RenderResult and module import)

• #​12340 94eaeea Thanks @​ematipico! - Fixes an issue where Astro actions didn't work when base was different from /

debug-js/debug (debug)

v4.4.0

Compare Source

Fixes (hopefully) the inefficient regex warnings in .enable().

Minor version as this is invariably going to break certain users who misuse the .enable() API and expected it to work with regexes, which was never supported nor documented. That's on you, sorry - that functionality won't be added back.

Full Changelog: debug-js/debug@4.3.7...4.4.0

evanw/esbuild (esbuild)

v0.24.2

Compare Source

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

v0.24.1

Compare Source

• 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:

  // The following code now transforms to "return true;\n"
  console.log(esbuild.transformSync(
    `return process.env['SOME-TEST-VAR']`,
    { define: { 'process.env["SOME-TEST-VAR"]': 'true' } },
  ))

  Note that if you're passing values like this on the command line using esbuild's --define flag, then you'll need to know how to escape quote characters for your shell. You may find esbuild's JavaScript API more ergonomic and portable than writing shell code.

• Minify empty try/catch/finally blocks (#​4003)

  With this release, esbuild will now attempt to minify empty try blocks:

  // Original code
  try {} catch { foo() } finally { bar() }
  
  // Old output (with --minify)
  try{}catch{foo()}finally{bar()}
  
  // New output (with --minify)
  bar();

  This can sometimes expose additional minification opportunities.

• Include entryPoint metadata for the copy loader (#​3985)

  Almost all entry points already include a entryPoint field in the outputs map in esbuild's build metadata. However, this wasn't the case for the copy loader as that loader is a special-case that doesn't behave like other loaders. This release adds the entryPoint field in this case.

• Source mappings may now contain null entries (#​3310, #​3878)

  With this change, sources that result in an empty source map may now emit a null source mapping (i.e. one with a generated position but without a source index or original position). This change improves source map accuracy by fixing a problem where minified code from a source without any source mappings could potentially still be associated with a mapping from another source file earlier in the generated output on the same minified line. It manifests as nonsensical files in source mapped stack traces. Now the null mapping "resets" the source map so that any lookups into the minified code without any mappings resolves to null (which appears as the output file in stack traces) instead of the incorrect source file.

  This change shouldn't affect anything in most situations. I'm only mentioning it in the release notes in case it introduces a bug with source mapping. It's part of a work-in-progress future feature that will let you omit certain unimportant files from the generated source map to reduce source map size.

• Avoid using the parent directory name for determinism (#​3998)

  To make generated code more readable, esbuild includes the name of the source file when generating certain variable names within the file. Specifically bundling a CommonJS file generates a variable to store the lazily-evaluated module initializer. However, if a file is named index.js (or with a different extension), esbuild will use the name of the parent directory instead for a better name (since many packages have files all named index.js but have unique directory names).

  This is problematic when the bundle entry point is named index.js and the parent directory name is non-deterministic (e.g. a temporary directory created by a build script). To avoid non-determinism in esbuild's output, esbuild will now use index instead of the parent directory in this case. Specifically this will happen if the parent directory is equal to esbuild's outbase API option, which defaults to the lowest common ancestor of all user-specified entry point paths.

• Experimental support for esbuild on NetBSD (#​3974)

  With this release, esbuild now has a published binary executable for NetBSD in the @esbuild/netbsd-arm64 npm package, and esbuild's installer has been modified to attempt to use it when on NetBSD. Hopefully this makes installing esbuild via npm work on NetBSD. This change was contributed by @​bsiegert.

  ⚠️ Note: NetBSD is not one of Node's supported platforms, so installing esbuild may or may not work on NetBSD depending on how Node has been patched. This is not a problem with esbuild. ⚠️

typicode/husky (husky)

v9.1.7

Compare Source

lint-staged/lint-staged (lint-staged)

v15.3.0

Compare Source

Minor Changes

• #​1495 e69da9e Thanks @​iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.

• #​1493 fa0fe98 Thanks @​iiroj! - Added more help messages around the automatic git stash that lint-staged creates as a backup (by default). The console output also displays the short git hash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing.

  For example:

  % npx lint-staged
  ✔ Backed up original state in git stash (20addf8)
  ✔ Running tasks for staged files...
  ✔ Applying modifications from tasks...
  ✔ Cleaning up temporary files...
  

  where the backup can be seen with git show 20addf8, or git stash list:

  % git stash list
  stash@{0}: lint-staged automatic backup (20addf8)
  

v15.2.11

Compare Source

Patch Changes

• #​1484 bcfe309 Thanks @​wormsik! - Escape paths containing spaces when using the "shell" option.

• #​1487 7dd8caa Thanks @​iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.

pnpm/pnpm (pnpm)

v9.15.2: pnpm 9.15.2

Compare Source

Patch Changes

• Fixed publish/pack error with workspace dependencies with relative paths #​8904. It was broken in v9.4.0 (398472c).
• Use double quotes in the command suggestion by pnpm patch on Windows #​7546.
• Do not fall back to SSH, when resolving a git-hosted package if git ls-remote works via HTTPS #​8906.
• Improve how packages with blocked lifecycle scripts are reported during installation. Always print the list of ignored scripts at the end of the output. Include a hint about how to allow the execution of those packages.

Platinum Sponsors

Gold Sponsors

v9.15.1

Compare Source

v9.15.0

Compare Source

v9.14.4

Compare Source

v9.14.3

Compare Source

v9.14.2

Compare Source

Patch Changes

• pnpm publish --json should work #​8788.

Platinum Sponsors

Gold Sponsors

Configuration 📅 Schedule: Branch creation - "* * * * 0,6" (UTC), Automerge - At any time (no schedule defined). 🚦 Automerge: Enabled. ♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired. If you want to rebase/retry this PR, check this box This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8ee4d8e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR