[create-svelte] [fix] todos failing to edit

[gtm-nayan]

closes #5350

HTTP methods are case sensitive, the fetch spec makes special considerations for some methods normalizing them to uppercase, but not PATCH.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

[changeset-bot]

🦋 Changeset detected

Latest commit: deec568

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

This PR includes changesets to release 1 package

Name	Type
create-svelte	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

[Conduitry]

... This makes me uncomfortable. Does undici require uppercase method names while node-fetch didn't? Needing this feels like a workaround, and I'd prefer trying to get to the bottom of what changed rather than fixing it here in the template project. We shouldn't expect everyone using SvelteKit to always be calling their APIs with upper-case methods.

[gtm-nayan]

Hmm, I think it was just patch that was 400-ing, so I didn't consider the switch from node-fetch to undici as a possible cause, but not completely off the table I guess. I'll do a quick sanity check.

[gtm-nayan]

Yeah, it's only patch that's affected, but looks like it is intended to be case-sensitive whatwg/fetch#50 and Undici being more spec compliant is likely what changed.

We shouldn't expect everyone using SvelteKit to always be calling their APIs with upper-case methods

For spec compliance we'd have to, and all uppercase seems to be the convention at least for the REST verbs. I'll uppercase the verbs on the api(..) calls to make it more explicit rather than tucking it away inside the function definition.