reroute-js 1.0.0-alpha.4 → 1.0.0-alpha.41

package/README.md

@@ -130,6 +130,7 @@ Reroute is a feature-rich file-based routing framework for building fullstack Re
   - `<Link>` - Client-side navigation with automatic prefetching (localizes content hrefs)
   - `<Image>` - Optimized images with automatic format negotiation and lazy loading
   - `<Outlet>` - Render nested route components
+  - Route groups - `routes/(app)/[layout].tsx` wraps the routes in `(app)/` with one layout, no URL segment
   - `<ContentRoute>` - Dynamic content rendering with metadata injection
   - `<ClientOnly>` - Client-side only rendering with optional layout preservation (className/style props)
 - 🎭 **Providers**:
@@ -144,6 +145,7 @@ Reroute is a feature-rich file-based routing framework for building fullstack Re
 - 🎨 **Format Control** - Support for auto, AVIF, WebP, JPEG, and PNG formats
 - 📐 **Responsive Images** - Automatic srcset generation for multiple device sizes (640-3840px)
 - ⚡ **On-Demand Processing** - Server-side image transformation using Sharp
+- 🧱 **Build-Time Preprocess** - Optional mobile / tablet / desktop bake at `reroute gen --prod`
 - 💾 **Smart Caching** - In-memory and disk cache for optimized images (1-year cache headers)
 - 🔍 **Lazy Loading** - Native lazy loading with IntersectionObserver fallback for older browsers
 - ⏫ **Priority Loading** - Opt-in eager loading for above-the-fold images
@@ -616,6 +618,8 @@ Files are loaded in order, with later files overriding earlier ones.
 - ❌ `DATABASE_URL` - Server-only
 - ❌ `SECRET_KEY` - Server-only
 
+A route's or layout's `ssr` (`data`, `head`, `lang`, `sitemap`) is server code too: the browser bundle leaves it out, with every import only `ssr` uses, so a loader can import a database client or call `Bun` freely. Declare it as `export const ssr = …` (or `const ssr = …; export { ssr }`); a form the build can't leave out fails it. When the browser navigates, the server sends the page's head and lang, built as for a full page load (layouts, `meta`, content and `ssr.head`), with its data; the browser swaps the page's own head for it.
+
 ### TypeScript Support
 
 For type safety, create a `env.d.ts` file:
@@ -670,7 +674,40 @@ src/client/routes/blog/content/
 - Flat files under `content/` are the default locale; nest under `content/{locale}/` for translations
 - Collections without locale folders behave as before
 - Default-locale prefix (`/blog/en-US/...`) 302s to the unprefixed URL
-- Optional negotiate: `Accept-Language` / cookie can 302 default content URLs to a localized path (`i18n.redirectContentOnNegotiate`, default `true`)
+- A locale segment in the URL always wins over cookie / `Accept-Language`
+- `setLocale()` writes `?lang=` and the server 302s to the canonical content URL (and sets the cookie). That is the only way to leave a URL that already has a locale in the path
+- Optional negotiate: `Accept-Language` / cookie can 302 **unprefixed** content URLs to a localized path (`i18n.redirectContentOnNegotiate`, default `true`)
+
+### Locale-prefixed pages (`i18n.prefixPages`)
+
+Off by default. With `prefixPages: true` every page carries its locale in the URL, so each response depends on its URL alone and a CDN that caches by URL never serves one visitor's language to the next:
+
+| URL | Locale |
+|-----|--------|
+| `/compare` | default |
+| `/pt-BR/compare`, `/pt-BR` | pt-BR |
+| `/help/pt-BR/slug` | pt-BR (content keeps its format) |
+
+- The cookie and `Accept-Language` never pick a page's locale, and page/data responses send no `Set-Cookie`
+- `/en-US/compare` 301s to `/compare`; a prefix in front of a content URL (`/pt-BR/help/slug`) 301s to `/help/pt-BR/slug`
+- `?lang=xx` 302s to that locale's URL (and only that redirect sets the cookie); `setLocale()` uses it
+- `<Link to="/compare">` renders `/pt-BR/compare` on a pt-BR page; a path that names a locale (`/pt-BR/...`) is left as written, and a link to another locale loads the document
+- `ssr.data` gets the full path as `pathname` (`/pt-BR/compare`), so data is keyed and cached per locale; routes, layouts and params match the unprefixed path
+- Every page gets `hreflang` alternates for each locale plus `x-default`; the sitemap lists each page once per locale
+- `unprefixedPaths: ['/portfolio', '/auth']`: pages that keep one URL for every locale (a PWA scope, a universal link, a payment return). `/portfolio` covers `/portfolio/...`, not `/portfolios`. A prefixed one (`/pt-BR/portfolio`) 301s to its bare URL; otherwise its locale comes from `?lang=`, the cookie or `Accept-Language`, as without `prefixPages`, and it may set the cookie, so don't let a CDN cache it. `Link` leaves them as written, they get no `hreflang`, and the sitemap lists them once. A link from a locale-prefixed page to one loads the document
+- `useRouter().routingPathname` is the path routes match (`/pt-BR/compare` → `/compare`): compare it, not `pathname`, to literals such as `'/'`
+
+#### One URL per page, the CDN picks the locale (`localeParam`)
+
+For pages shared as one link (a public profile), where `/pt-BR/...` URLs don't fit: a CDN reads the visitor's language and adds it as a query parameter that is part of its cache key, and the page renders in that locale.
+
+```ts
+i18n: { localeParam: '__locale' },
+```
+
+- The page's locale is that parameter (a content URL's segment still wins), else the default. The cookie, `Accept-Language` and `?lang=` are never read, nothing redirects and no cookie is set, so each response is a function of its URL and the CDN may cache it
+- The CDN adds the parameter to every request, `/__reroute_data` included (reroute reads it from the data request's own query). With Cloudflare, a URL Rewrite Transform Rule: when `starts_with(lower(http.request.headers["accept-language"][0]), "pt")`, set the query to `concat(http.request.uri.query, "&__locale=pt-BR")`
+- Without the CDN (local dev), pages render in the default locale; add `?__locale=pt-BR` to see another
 
 ### UI Strings
 
@@ -713,6 +750,9 @@ export default defineConfig({
     localesDir: 'locales',               // catalog directory
     cookie: 'reroute-locale',
     redirectContentOnNegotiate: true,   // 302 default content → localized URL
+    prefixPages: false,                 // true: /pt-BR/compare, URL-only locale
+    unprefixedPaths: [],                // with prefixPages: paths never prefixed
+    localeParam: '',                    // '__locale': a CDN names the locale in the query
   },
 });
 ```
@@ -1165,8 +1205,9 @@ export default defineConfig({
 Your site now supports:
 - `.txt` and `.md` extensions on any route (e.g., `/blog/post.txt`, `/about.md`)
 - Accept header content negotiation (`Accept: text/plain`, `Accept: text/markdown`)
-- `/llms.txt` - Index of all content organized by section
-- `/llms-full.txt` - Complete site content in one file
+- `/llms.txt` - Index of all content: title, description, and link per page
+- `/llms-full.txt` - Complete site content in one file (optional; large)
+- HTML discovery: `Link: rel=alternate` + `<link type="text/markdown">` pointing at the `.md` twin, `Link: rel=llms-txt`, `Vary: Accept`, and `Content-Signal` (also a `Content-Signal:` line in `robots.txt` when robots is enabled)
 
 #### How It Works
 
@@ -1199,6 +1240,7 @@ curl -H "Accept: text/html" https://example.com/blog/hello-world  # Default
 - **Flexible exclusions** - Strings, RegExp, or custom functions
 - **Works everywhere** - Collections, SSR routes, static pages
 - **Auto-discovery** - All content automatically indexed
+- **Crawler hints** - HTML `Link` / `<link rel="alternate">`, `Content-Signal`, `Vary: Accept`
 
 #### Discovering LLM Files in Your UI
 

package/cli/bin.d.ts

@@ -1,5 +1,5 @@
 /**
- * reroute-js v1.0.0-alpha.4
+ * reroute-js v1.0.0-alpha.41
  *
  * @license MIT
  * @copyright 2026 stewones <hi@stewan.io>