A different emphasis.
WHAT IT EMPHASISES
Working with the web platform rather than around it.
WHAT THAT MEANS PRACTICALLY
Forms submit as forms Data loading is tied to routes Progressive enhancement is the default assumption
WHAT THAT PROVIDES
Applications that function without JavaScript, then improve with it.
WHY THAT MATTERS
Reliability on poor connections and modest devices.
WHAT THE CORE CONCEPTS ARE
Loaders, providing data to a route Actions, handling mutations Nested routes, each with their own data and error handling
WHAT NESTED ROUTES PROVIDE
Parts of a page loading and failing independently.
WHY THAT MATTERS
One failing section does not take down the whole page.
WHAT IT HANDLES WELL
Forms and mutations Error boundaries per route Revalidating data after changes
WHAT TO ESTABLISH BEFORE CHOOSING IT
Whether your hosting supports the runtime it needs.
WHAT SUITS IT
Applications with substantial form interaction and data mutation.
WHAT TO TAKE FROM IT REGARDLESS
The principle that the platform should be worked with, not replaced.
