I'm using pnpm and the catalog feature.
It's nice in monorepos to manage deps & version in one place. (+ you can name & group deps)

In package.json:

{
  "peerDependencies": {
    "svelte": "catalog:svelte-dep"
  }  
}

An in pnpm-workspace.yaml

catalogs:
  # adding comment is GREAT!
  svelte-dep:
    'svelte': '^5.0.0'
  
  # this is the stuff bla bla bla
  sveltekit:
    '@sveltejs/kit': '2.17.3'
    '@sveltejs/package': '2.3.7'
    '@sveltejs/vite-plugin-svelte': '5.0.1'
    '@sveltejs/adapter-auto': '4.0.0'
    '@sveltejs/adapter-node': '5.2.12'

BUT, it's not semver standard. :( (Maybe one day?)

That's why I would suggest this fix ?
Feel free to le me know what do you think

Please don't delete this checklist! 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
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

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

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

• Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.