Content-type specific loaders

[joshnuss]

Background

SvelteKit loads data imperatively through +page.js and +page.server.js.

Idea

We could support non-imperative loading too, based on the extension of +page.??? and +page.server.???.

For example, if I want my page to backed by JSON, I would define a .json file instead:

in +page.json:

{
  "title": "About us",
  "summary": "bla bla bla"
}

Then the loading logic could be implied as:

// don't have to write this
import * as data from './+page.json'

export function load() {
  return data;
}

The user wouldn't have to write the loader, it would be provided based on the extension type. .csv -> CSVLoader.

Same idea would work for .json, .csv, .graphql, .sql etc..

Why?

• It's easy for beginners
• It's less code
• It provides a declarative path
• Less JavaScript
• It makes it possible to use SvelteKit as a CMS where data is co-located

Why not?

• Another thing to teach
• Some pages need multiple pieces of content and this approach implies one