Conversation
@sveltejs/kit was declared as an optional peer with a "*" range, causing npm to auto-install the newest @sveltejs/kit and pull in its transitive @sveltejs/vite-plugin-svelte → vite peer chain. In non-SvelteKit projects already on Vite 7 (via Vitest, Storybook, etc.) this produced a hard ERESOLVE error requiring `npm install --force`. Move @sveltejs/kit to devDependencies so the sveltekit entrypoint still builds and type-generates in the monorepo. SvelteKit consumers always have @sveltejs/kit installed as the framework, so flags/sveltekit continues to resolve it from their own tree. fixes #440
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
chriswdmr
approved these changes
Jul 24, 2026
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@sveltejs/kit was declared as an optional peer with a "*" range, causing npm to auto-install the newest @sveltejs/kit and pull in its transitive @sveltejs/vite-plugin-svelte → vite peer chain. In non-SvelteKit projects already on Vite 7 (via Vitest, Storybook, etc.) this produced a hard ERESOLVE error requiring
npm install --force.Move @sveltejs/kit to devDependencies so the sveltekit entrypoint still builds and type-generates in the monorepo. SvelteKit consumers always have @sveltejs/kit installed as the framework, so flags/sveltekit continues to resolve it from their own tree.
fixes #440