+config.js or +config.json

[TranscendentalRide]

With time it seems that the variety of way to render a route can grow feature rich. Would it not better scale to have route-based configuration than to add various ornaments to path names or relying on special / untyped / unclear variable value exports from +page.js etc.?

Here is the thing, template name in routes makes refactoring harder. Naming is difficult and updating the name of a template is inevitable. If changing the name of a template created type errors, it would be easy to know where to update.

+config.js

let config: Config = {
  prerender: true,
  template: 'foo' // typed, breaks build if template name changed
}
export default config