@ossy/app 0.15.13 → 1.0.1

package/README.md

@@ -25,11 +25,7 @@ For a single-file setup, use `src/pages.jsx` (legacy).
 
 Split pages are merged into **`build/.ossy/pages.generated.jsx`** (next to other build output) during `dev` / `build`.
 
-List **`modules: ['@your/npm-package', ...]`** in `src/config.js` to pull in every **`*.page.js`**, **`*.page.jsx`**, **`*.page.ts`**, and **`*.page.tsx`** file under each package’s **`src/`** tree (any subfolder). Deprecated: **`pagesModules`** / **`pagesModule`** — still read for now, with a deprecation warning.
-
-Optional **`src/page-shell.jsx`** (or `.js`): default export your site layout component. **`usePageShell()`** from `@ossy/connected-components` wraps module pages in that shell so packages do not import site paths.
-
-**Note:** **`@ossy/connected-components`** is slated for retirement; its responsibilities (app shell, routing wrapper, **`usePageShell`**, etc.) should move into **`@ossy/app`** or smaller focused packages over time. See that package’s README.
+**Client JS (per-page):** For each `*.page.jsx`, the build emits **`build/.ossy/hydrate-<pageId>.jsx`** → **`public/static/hydrate-<pageId>.js`**. The HTML for a request only loads the hydrate script for the **current** route (full document navigation), so other pages’ components are not part of that entry. React and shared dependencies still go into hashed shared chunks. The inline config (`window.__INITIAL_APP_CONFIG__`) no longer includes the full `pages` list—only request-time fields (theme, `apiUrl`, etc.).
 
 Add `src/config.js` for workspace and theme:
 
@@ -47,17 +43,15 @@ Config is loaded at build time and merged with request-time settings (e.g. user
 
 Run `npx @ossy/cli dev` or `npx @ossy/cli build`.
 
+If the package has **`src/resource-templates/`**, the build also writes **`.ossy-system-templates.generated.js`** there (merging `*.resource.js` into `SystemTemplates`, ordered by filename).
+
 ## API routes
 
 Define HTTP handlers as an array of `{ id, path, handle(req, res) }` objects (same shape the server passes to `@ossy/router`).
 
-**Split files (recommended):** add any number of `*.api.js` (or `.api.mjs` / `.api.cjs`) files under `src/` (nested dirs allowed). Each file’s **default export** is either one route object or an array of routes. They are merged: `src/api.js` first (if present), then each `*.api.js` in lexicographic file path order.
-
-**Legacy single file:** `src/api.js` default export is still supported. If it exists, its routes are merged **first**, then every `*.api.js`.
-
-At build/dev time this becomes **`build/.ossy/api.generated.js`** (under your `--destination` / `build` output, typically gitignored with the rest of `build/`) whenever you have `src/api.js` and/or any `*.api.js`, so the Rollup entry stays stable when you add or remove split files.
+Add any number of `*.api.js` (or `.api.mjs` / `.api.cjs`) files under `src/` (nested dirs allowed). Each file’s **default export** is either one route object or an array of routes. Files are merged in lexicographic path order.
 
-**Override:** pass `--api-source ./path/to/file.js` to use a single file and skip discovery.
+Build/dev always writes **`build/.ossy/api.generated.js`** (typically gitignored with `build/`). With no API files it exports an empty array.
 
 Example `src/health.api.js`:
 
@@ -71,20 +65,6 @@ export default {
 }
 ```
 
-Example `src/api.js` (optional aggregate or empty `[]`):
-
-```js
-export default [
-  {
-    id: 'users',
-    path: '/api/users',
-    handle(req, res) {
-      res.json({ users: [] })
-    },
-  },
-]
-```
-
 API routes are matched before the app is rendered. The router supports dynamic segments (e.g. `path: '/api/users/:id'`); extract params from `req.originalUrl` if needed. Use paths that don't conflict with `/@ossy/*` (reserved for the internal proxy).
 
 ## Background worker tasks (`*.task.js`)