chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
dts-buddy	^0.5.5 -> ^0.6.0
pnpm (source)	10.6.4 -> 10.8.0
sharp (source, changelog)	^0.33.5 -> ^0.34.0

---

Release Notes

Rich-Harris/dts-buddy (dts-buddy)

v0.6.0

Compare Source

Minor Changes

• 87276ef: feat: support export { ... as default } from ...

Patch Changes

• 87276ef: fix: improve sourcemaps

pnpm/pnpm (pnpm)

v10.8.0

Compare Source

Minor Changes

• Experimental. A new hook is supported for updating configuration settings. The hook can be provided via .pnpmfile.cjs. For example:

  module.exports = {
    hooks: {
      updateConfig: (config) => ({
        ...config,
        nodeLinker: "hoisted",
      }),
    },
  };

• Now you can use the pnpm add command with the --config flag to install new configurational dependencies #​9377.

Patch Changes

• Do not hang indefinitely, when there is a glob that starts with !/ in pnpm-workspace.yaml. This fixes a regression introduced by #​9169.
• pnpm audit --fix should update the overrides in pnpm-workspace.yaml.
• pnpm link should update overrides in pnpm-workspace.yaml, not in package.json #​9365.

v10.7.1: pnpm 10.7.1

Compare Source

Patch Changes

• pnpm config set should convert the settings to their correct type before adding them to pnpm-workspace.yaml #​9355.
• pnpm config get should read auth related settings via npm CLI #​9345.
• Replace leading ~/ in a path in .npmrc with the home directory #​9217.

Platinum Sponsors

Gold Sponsors

v10.7.0

Compare Source

Minor Changes

• pnpm config get and list also show settings set in pnpm-workspace.yaml files #​9316.

• It should be possible to use env variables in pnpm-workspace.yaml setting names and value.

• Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range * is the same as name-only, except that patch application failure will not be ignored.

  For example:

  patchedDependencies:
    foo: patches/foo-1.patch
    foo@^2.0.0: patches/foo-2.patch
    [email protected]: patches/foo-3.patch

  The above configuration would apply patches/foo-3.patch to [email protected], patches/foo-2.patch to all foo versions which satisfy ^2.0.0 except 2.1.0, and patches/foo-1.patch to the remaining foo versions.

  [!WARNING]
  The version ranges should not overlap. If you want to specialize a sub range, make sure to exclude it from the other keys. For example:

  # pnpm-workspace.yaml
  patchedDependencies:
    # the specialized sub range
    '[email protected]': patches/foo.2.2.0-2.8.0.patch
    # the more general patch, excluding the sub range above
    'foo@>=2.0.0 <2.2.0 || >2.8.0': 'patches/foo.gte2.patch

  In most cases, however, it's sufficient to just define an exact version to override the range.

• pnpm config set --location=project saves the setting to a pnpm-workspace.yaml file if no .npmrc file is present in the directory #​9316.

• Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.

• Add pnpm.ignorePatchFailures to manage whether pnpm would ignore patch application failures.

  If ignorePatchFailures is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.

  If ignorePatchFailures is explicitly set to false, pnpm would throw an error when any type of patch fails to apply.

  If ignorePatchFailures is explicitly set to true, pnpm would print a warning when any type of patch fails to apply.

Patch Changes

• Remove dependency paths from audit output to prevent out-of-memory errors #​9280.

v10.6.5

Compare Source

lovell/sharp (sharp)

v0.34.1

Compare Source

v0.34.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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: 56cda98

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

[svelte-docs-bot]

Preview: https://svelte-dev-git-preview-kit-13611-svelte.vercel.app/

[github-actions]

pnpm add https://pkg.pr.new/@sveltejs/adapter-auto@13611
pnpm add https://pkg.pr.new/@sveltejs/adapter-cloudflare@13611
pnpm add https://pkg.pr.new/@sveltejs/adapter-node@13611
pnpm add https://pkg.pr.new/@sveltejs/adapter-static@13611
pnpm add https://pkg.pr.new/@sveltejs/adapter-netlify@13611
pnpm add https://pkg.pr.new/@sveltejs/adapter-vercel@13611
pnpm add https://pkg.pr.new/@sveltejs/amp@13611
pnpm add https://pkg.pr.new/create-svelte@13611
pnpm add https://pkg.pr.new/@sveltejs/enhanced-img@13611
pnpm add https://pkg.pr.new/@sveltejs/kit@13611
pnpm add https://pkg.pr.new/@sveltejs/package@13611