Linting is failing because of a TS error in the following:

<a id="one" href="/data-sveltekit/replacestate/target" data-sveltekit-replacestate>one</a>

I couldn't find where I would make the appropriate updates to fix this. I tried looking for corresponding data-sveltekit-noscroll TS definitions but didn't find anything. All I could find are some generated types in test-tmp/.../elements/index.d.ts:

// SvelteKit
'data-sveltekit-noscroll'?: true | '' | 'off' | undefined | null;
'data-sveltekit-preload-code'?: true | '' | 'eager' | 'viewport' | 'hover' | 'tap' | 'off' | undefined | null;
'data-sveltekit-preload-data'?: true | '' | 'hover' | 'tap' | 'off' | undefined | null;
'data-sveltekit-reload'?: true | '' | 'off' | undefined | null;

Just had another little look at this and realised the corresponding types are within sveltejs/language-tools.

I can make a PR there too but I'm not sure what the process is for ensuring the changes to both would be released in sync?

Update: PR within language-tools here: sveltejs/language-tools#1865

@dummdidumm what's the process for merging in changes across the 3 repos this affects? Will updates to sveltejs/language-tools and sveltejs/svelte get published first and then we can move forward with this PR?

Is there anything else I can do to help on this PR here?

Yes we will likely merge Svelte/language-tools first.

That said - since you now nicely laid out all the needed PRs across the repos, would you be open to also adding data-sveltekit-keepfocus (would close #7895)? Then we'd have parity with the goto options. (you don't need to add a test for this in my opinion, it's already covered through testing goto)

Sure, I'll try and have a look in the next few days.

I've added -keepfocus, and also made changes for the form handlers. As I said before, I'm not too well versed in Sveltekit forms yet so might be worth checking that part of the PR a bit more closely!