New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[chore] introduce KitConfig
type
#5141
Conversation
🦋 Changeset detectedLatest commit: 92c6b10 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
KitConfig
type
Should we change /** @type {import('@sveltejs/kit').UserConfig} */ ...feels a bit more natural than this, to me: /** @type {import('@sveltejs/kit').KitConfig} */ Presumably |
I took the liberty of making that change; we can revert c0bcc3b if you disagree with it |
I feel like it will be confusing to have two |
This reverts commit c0bcc3b.
fair enough. reverted |
Creates a
KitConfig
andValidatedKitConfig
(last file in the PR) to start to decouple the Svelte and SvelteKit configuration. We will need to figure out what to do aboutextensions
which stops us from being able to more thoroughly convert toValidatedKitConfig