chore(dev): test against SvelteKit 2.69 (dev-dep only)#7
Merged
Conversation
…55.0) Adds @sveltejs/kit@^2.69.3 as a devDependency so CI/build/typecheck run against the current SvelteKit instead of the lockfile-pinned 2.55.0. The peerDependency is left at ^2.55.0 — the library only uses long-stable APIs, so there's no reason to raise the floor and force consumers on 2.55–2.68 to upgrade. The peer will be bumped in a later PR that actually adopts newer remote-function features (submitted, RemoteFormEnhanceInstance, …). Build + 107 tests + typecheck all green against 2.69.3. No version bump.
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
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.
Bumps the dev SvelteKit to the latest (
@sveltejs/kit@^2.69.3) so CI/build/typecheck run against current SvelteKit — the lockfile was pinning 2.55.0, so we weren't actually testing against recent releases.The
peerDependencyis intentionally left at^2.55.0. The library only uses long-stable APIs (error, and the$app/serverremote functionsquery/command/form), so raising the peer floor would only force consumers on 2.55–2.68 to upgrade (pnpm-strict install errors / npm warnings) for no functional gain.This is the first of two: a follow-up PR will adopt newer remote-function features (e.g. the
submittedproperty from 2.69,RemoteFormEnhanceInstance/RemoteFormEnhanceCallbacktypes from 2.68, theexactOptionalPropertyTypesform fix from 2.67) and then raise the peer floor to match — that break will be justified because the code will actually require it.Verified
Build, 107 runtime tests, and the type-check suite (which validates
RemoteFormInputcompatibility) all pass against SvelteKit 2.69.3. No version bump.