chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/partytown (source)	2.1.0 -> 2.1.1
@typescript-eslint/eslint-plugin (source)	7.12.0 -> 7.13.0
@typescript-eslint/parser (source)	7.12.0 -> 7.13.0
astro (source)	4.10.1 -> 4.10.2
esbuild	0.21.4 -> 0.21.5
lint-staged	15.2.5 -> 15.2.7
pnpm (source)	9.2.0 -> 9.3.0
prettier (source)	3.3.1 -> 3.3.2
vite (source)	5.2.13 -> 5.3.1

---

Release Notes

withastro/astro (@​astrojs/partytown)

v2.1.1

Compare Source

Patch Changes

• #​11083 416c4ac Thanks @​V3RON! - Prevent Partytown from crashing when View Transitions are enabled

  When View Transitions are turned on, Partytown executes on every transition.
  It's not meant to be like that, and therefore it breaks the integration completely.
  Starting from now, Partytown will be executed only once.

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v7.13.0

Compare Source

🚀 Features

• typescript-estree: require import = require() argument to be a string literal

• typescript-estree: forbid .body, .async, .generator on declare function

• eslint-plugin: [no-dynamic-delete] allow all string literals as index

🩹 Fixes

• ast-spec: function-call-like callee should be Expression not LeftHandSideExpression

• scope-manager: handle index signature in class

• eslint-plugin: [init-declarations] refine report locations

• eslint-plugin: [no-base-to-string] make error message more nuanced

• eslint-plugin: [no-unsafe-assignment] be more specific about error types

• eslint-plugin: [no-magic-numbers] fix implementation of the ignore option

❤️ Thank You

• Fotis Papadogeorgopoulos
• Joshua Chen
• Kirk Waiblinger
• Tobiloba Adedeji
• Vinccool96
• YeonJuan

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v7.13.0

Compare Source

🚀 Features

• parser, typescript-estree: export withoutProjectParserOptions utility

❤️ Thank You

• Fotis Papadogeorgopoulos
• Joshua Chen
• Kirk Waiblinger
• Tobiloba Adedeji
• Vinccool96
• YeonJuan

You can read about our versioning strategy and releases on our website.

withastro/astro (astro)

v4.10.2

Compare Source

Patch Changes

• #​11231 58d7dbb Thanks @​ematipico! - Fixes a regression for getViteConfig, where the inline config wasn't merged in the final config.

• #​11228 1e293a1 Thanks @​ascorbic! - Updates getCollection() to always return a cloned array

• #​11207 7d9aac3 Thanks @​ematipico! - Fixes an issue in the rewriting logic where old data was not purged during the rewrite flow. This caused some false positives when checking the validity of URL path names during the rendering phase.

• #​11189 75a8fe7 Thanks @​ematipico! - Improve error message when using getLocaleByPath on path that doesn't contain any locales.

• #​11195 0a6ab6f Thanks @​florian-lefebvre! - Adds support for enums to astro:env

  You can now call envField.enum:

  import { defineConfig, envField } from 'astro/config';
  
  export default defineConfig({
    experimental: {
      env: {
        schema: {
          API_VERSION: envField.enum({
            context: 'server',
            access: 'secret',
            values: ['v1', 'v2'],
          }),
        },
      },
    },
  });

• #​11210 66fc028 Thanks @​matthewp! - Close the iterator only after rendering is complete

• #​11195 0a6ab6f Thanks @​florian-lefebvre! - Adds additional validation options to astro:env

  astro:env schema datatypes string and number now have new optional validation rules:

  import { defineConfig, envField } from 'astro/config';
  
  export default defineConfig({
    experimental: {
      env: {
        schema: {
          FOO: envField.string({
            // ...
            max: 32,
            min: 3,
            length: 12,
            url: true,
            includes: 'foo',
            startsWith: 'bar',
            endsWith: 'baz',
          }),
          BAR: envField.number({
            // ...
            gt: 2,
            min: 3,
            lt: 10,
            max: 9,
            int: true,
          }),
        },
      },
    },
  });

• #​11211 97724da Thanks @​matthewp! - Let middleware handle the original request URL

• #​10607 7327c6a Thanks @​frankbits! - Fixes an issue where a leading slash created incorrect conflict resolution between pages generated from static routes and catch-all dynamic routes

evanw/esbuild (esbuild)

v0.21.5

Compare Source

• Fix Symbol.metadata on classes without a class decorator (#​3781)

  This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

• Allow unknown import attributes to be used with the copy loader (#​3792)

  Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

  // This is an error with "--bundle" without also using "--external:./bagel.js"
  import tasty from "./bagel.js" with { type: "bagel" }

  Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

  However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

  // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
  import tasty from "./tasty.bagel" with { type: "bagel" }

• Support import attributes with glob-style imports (#​3797)

  This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

  async function loadLocale(locale: string): Locale {
    const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
    return unpackLocale(locale, data)
  }

  Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

  ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data
  
      example.ts:2:28:
        2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
          ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  In addition, this change means plugins can now access the contents of with for glob-style imports.

• Support ${configDir} in tsconfig.json files (#​3782)

  This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

  {
    "compilerOptions": {
      "paths": {
        "js/*": ["${configDir}/dist/js/*"]
      }
    }
  }

  You can read more in TypeScript's blog post about their upcoming 5.5 release. Note that this feature does not make use of template literals (you need to use "${configDir}/dist/js/*" not `${configDir}/dist/js/*`). The syntax for tsconfig.json is still just JSON with comments, and JSON syntax does not allow template literals. This feature only recognizes ${configDir} in strings for certain path-like properties, and only at the beginning of the string.

• Fix internal error with --supported:object-accessors=false (#​3794)

  This release fixes a regression in 0.21.0 where some code that was added to esbuild's internal runtime library of helper functions for JavaScript decorators fails to parse when you configure esbuild with --supported:object-accessors=false. The reason is that esbuild introduced code that does { get [name]() {} } which uses both the object-extensions feature for the [name] and the object-accessors feature for the get, but esbuild was incorrectly only checking for object-extensions and not for object-accessors. Additional tests have been added to avoid this type of issue in the future. A workaround for this issue in earlier releases is to also add --supported:object-extensions=false.

okonet/lint-staged (lint-staged)

v15.2.7

Compare Source

Patch Changes

• #​1440 a51be80 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version drops the --path-format=absolute option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading git to the latest version.

v15.2.6

Compare Source

Patch Changes

• #​1433 119adb2 Thanks @​iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.

pnpm/pnpm (pnpm)

v9.3.0

Compare Source

Minor Changes

• Semi-breaking. Dependency key names in the lockfile are shortened if they are longer than 1000 characters. We don't expect this change to affect many users. Affected users most probably can't run install successfully at the moment. This change is required to fix some edge cases in which installation fails with an out-of-memory error or "Invalid string length (RangeError: Invalid string length)" error. The max allowed length of the dependency key can be controlled with the peers-suffix-max-length setting #​8177.

Patch Changes

• Set reporter-hide-prefix to true by default for pnpm exec. In order to show prefix, the user now has to explicitly set reporter-hide-prefix=false #​8174.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

prettier/prettier (prettier)

v3.3.2

Compare Source

diff

Fix handlebars path expressions starts with @ (#​16358 by @​Princeyadav05)

{{! Input }}
<div>{{@&#8203;x.y.z}}</div>

{{! Prettier 3.3.1 }}
<div>{{@&#8203;x}}</div>

{{! Prettier 3.3.2 }}
<div>{{@&#8203;x.y.z}}</div>

vitejs/vite (vite)

v5.3.1

Compare Source

• fix(build): handle preload treeshaking for braces (#​17479) (d355568), closes #​17479
• fix(build): handle preload treeshaking for commas (#​17472) (3e27071), closes #​17472
• fix(build): preload treeshaking ignore equal (#​17480) (6ced135), closes #​17480
• chore: consolidate changelog for 5.3 (#​17476) (1f09344), closes #​17476

v5.3.0

Compare Source

• fix: typo in client log (#​17363) (68aa9f8), closes #​17363
• fix(ssrTransform): handle arbitrary module namespace identifiers (#​17446) (0a76652), closes #​17446
• test: disable isolate for unit test (#​17448) (f16fae5), closes #​17448
• feat: asset type add bmp (#​17439) (ec287f8), closes #​17439

---

Configuration

📅 Schedule: Branch creation - "every weekend" (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 has been generated by Mend Renovate. View repository job log here.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c0ee35e

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