Skip to content

fix(migrate): allow @sveltejs/kit to be a dependency - #1274

Closed
sacrosanctic wants to merge 2 commits into
sveltejs:version-1from
sacrosanctic:lossen-kit-check-on-migration
Closed

fix(migrate): allow @sveltejs/kit to be a dependency#1274
sacrosanctic wants to merge 2 commits into
sveltejs:version-1from
sacrosanctic:lossen-kit-check-on-migration

Conversation

@sacrosanctic

Copy link
Copy Markdown
Contributor

Closes #1270

Description

A migration is not the right place to police this.

Checklist

  • Update snapshots (if applicable)
  • Add a changeset (if applicable)
  • Allow maintainers to edit this PR
  • I care about what I'm doing, no matter the tool I use (Notepad, Sublime, VSCode, AI...)

@pkg-svelte-dev

pkg-svelte-dev Bot commented Aug 14, 2026

Copy link
Copy Markdown

Install the latest version of sv from 55d2b5b:

pnx https://pkg.svelte.dev/sv/c/55d2b5bfdc5bcafe863960667190639ff66ee338 create

Open in pkg.svelte.dev: https://pkg.svelte.dev/repos/cli/pr/1274

Note

This PR is from a fork. A maintainer must approve approve each commit before it can be built and installed.

@changeset-bot

changeset-bot Bot commented Aug 14, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 55d2b5b

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

This PR includes changesets to release 1 package
Name Type
sv 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

@manuel3108

Copy link
Copy Markdown
Member

I don't think this is necessary. Also the issue describes a really special case that we should not support IMHO.

@manuel3108 manuel3108 closed this Aug 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

@sveltejs/kit is not a devDependency

2 participants