add routes command

[creeefs]

Add svelte-kit routes command

While reading #738, I thought adding a svelte-kit routes command would be a helpful command to help mitigate the difficulty of knowing what routes are available as the file structure grows. The current version of the PR is very crude (i.e. just prints the route objects), but if the team finds this useful, we could prettify the output. Additionally, I can see this command helping users understand trickier route behavior (e.g. "fallthrough" routes).

Example

> svelte-kit routes

[
  {
    type: 'page',
    pattern: /^\/$/,
    params: [],
    parts: [ 'src/routes/index.svelte' ]
  },
  {
    type: 'endpoint',
    pattern: /^\/about\/?$/,
    file: 'src/routes/about.js',
    params: []
  },
  {
    type: 'page',
    pattern: /^\/about\/?$/,
    params: [],
    parts: [ 'src/routes/about.svelte' ]
  }
]

Inspiration for this comes from rails routes.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/sveltejs/kit/ECJEcBsPva5BxF9uLVNYwCKdMbBg
✅ Preview: Canceled

[Deployment for 20227a5 canceled]

[benmccann]

One alternative idea, should we provide some built-in page to handle this in dev mode?

[Conduitry]

A benefit of having it be a page is that we could make it be like a 'routes playground' thing, where you can see what things in what order would be attempted to use to display the page for a given URL.

[creeefs]

Yea, I think a page could be really cool too. Swagger docs allow you to test your endpoints easily. I think there are good use cases for both a cli command as well as a web page.

[benmccann]

Thanks for sharing this idea! Since we'd still need to work out exactly what we want this to look like, it's probably best to have the discussion in an issue. I'm going to close this as a result so that we can keep the PR queue clean