Named routes or Typesafe Routes or Route Resolution

[airtonix]

In most other server side frameworks the routes are defined as variables by the codebase (Django, Express, Nest, etc).

Amongst those, Nest and Django have inbuilt ways for a route to have an alias.., a name (or even in Djangos case... a namespace); So that referring to it elsewhere through out the codebase is not intertwined with what the route pattern actually is.

Django and Python have some idiosyncrasies around sharing variables and imports etc, so they leaned heavily on giving routes names.

Over in typescript land, people prefer to use route patterns as exported functions or lean on typesafety for guardrails.

Since Nitro routing has folder based, Remix Routes is a good example of what Nitro should aim for.