chore: bump dts-buddy

[Rich-Harris]

A recent (and slightly embarrassing) revelation — we are currently exposing our private junk in addition to all our public interfaces. It turns out that these are not the same:

declare module 'x' {
  type a = {...};
  export type b = {...};
}

declare module 'x' {
  type a = {...};
  type b = {...};

  export { b };
}

In the first case, for reasons I cannot begin to fathom, TypeScript exposes everything, not just the things that were explicitly marked with the export keyword. In the second case, sanity prevails.

dts-buddy, which generates our bundle of types, was recently fixed to always use the second form. This is technically a breaking change insofar as someone might have depended on a 'private' (and undocumented) type.

Before submitting the PR, please make sure you do the following

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• Prefix your PR title with feat:, fix:, chore:, or docs:.
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests and linting

• Run the tests with pnpm test and lint the project with pnpm lint

[changeset-bot]

🦋 Changeset detected

Latest commit: 79d3bf8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
svelte	Patch

Not sure what this means? Click here to learn what changesets are.

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

[dummdidumm]

Thanks to Mateusz I also found out why the behavior is that way. TLDR: Historical reasons; it was an accident it was ever allowed but to not break the world export type ..; type ..; still works "wrong" today while export { .. } "fixes" it. microsoft/TypeScript#58912 (review)