(feat) create sveltekit route files

[david-plugge]

• create a single page/layout/error/endpoint
• create multiple files at once
• enter url path for the file location
• use WorkspaceEdit instead of fs
• find out if this is really a SvelteKit app (check package.json)
• ask if a matcher should be created if found in the path and does not exist
• only show the explorer menu in the routes folder (don´t know if this is possible, or needed)
• read svelte.config.js because people can customize the routes folder (?) (maybe later, not sure how feasible this is since we need to read a JS file)

[dummdidumm]

From reading the bullet point list it sounds like we only need to do the package.json check, or maybe not even that because it's a dedicated command someone actively needs to invoke, and that someone likely doesn't do that in a non-Kit app. I'm ok with doing the other stuff later. Thoughts?

[david-plugge]

I totally agree, it just adds unnecessary complexity.

[david-plugge]

I also added some snippets for RequestHandler and Load functions.
Is it fine to include them in this PR?
Or do you think we should not add any kit related snippets?

Edit: Not sure why but none of the snippets seem to work, even the svelte ones.

[dummdidumm]

Prefixes were deliberately left out in #1373 so they don't conflict with the language server completions. It sounds like you were wondering why they didn't show up, that's why. Could you revert this change?

[david-plugge]

Does this only affect the svelte snippets? The js and ts snippets don´t work for me without the prefix

[dummdidumm]

yes, only Svelte snippets

[dummdidumm]

Apart from the snippet thing (prefix was omitted deliberatly) this seems like it's ready to review?

[dummdidumm]

Awesome work! Fixed one bug which made it fail on Windows, but that's all. Thank you so much for working on this 🎉