@ecopages/core 0.2.0-beta.9 → 0.2.0-rc.0

package/README.md

@@ -18,6 +18,7 @@ The current core package is organized around app-owned runtime state and explici
 The important ownership rules are:
 
 - `ConfigBuilder.build()` finalizes app-owned build and runtime services.
+- Component identity attribution is one shared source transform for server, browser, and HMR compilation paths: after a lexical `eco.` gate, it uses Oxc to wrap supported factory options with `bindComponentIdentity()`, which factories retain as `config.identity`.
 - browser bundling and server module loading are explicit, separate paths.
 - runtime hosts stay thin and delegate framework work into core services.
 - HMR and invalidation use shared graph-aware services instead of runtime-specific ad hoc wiring.
@@ -82,6 +83,7 @@ Use this package README as the top-level map, then drill into the focused subsys
 - `src/build/README.md`: build adapter, executor, and development build coordination
 - `src/services/README.md`: cross-cutting runtime services and orchestration helpers
 - `src/adapters/README.md`: Bun, Node, and shared adapter boundaries
+- `src/dev/README.md`: dev transform server and on-demand client delivery
 - `src/hmr/README.md`: HMR strategy and update-layer ownership
 - `src/router/README.md`: route discovery, matching, and browser navigation coordination
 - `src/route-renderer/README.md`: rendering orchestration and dependency resolution
@@ -114,7 +116,7 @@ Configure your integratons, processors, and default metadata. Ecopages uses a bu
 
 ```typescript
 import { ConfigBuilder } from '@ecopages/core/config-builder';
-// import your desired plugins...
+import { ecopagesJsxPlugin } from '@ecopages/ecopages-jsx';
 
 const config = await new ConfigBuilder()
 	.setRootDir(import.meta.dirname)
@@ -123,7 +125,7 @@ const config = await new ConfigBuilder()
 		title: 'My Ecopages Site',
 		description: 'Built with Ecopages',
 	})
-	// .setIntegrations([kitajsPlugin()])
+	.setIntegrations([ecopagesJsxPlugin()])
 	.build();
 
 export default config;
@@ -186,31 +188,60 @@ Dependency ownership affects final asset packaging:
 
 ### 5. API Handlers
 
-Add server-side routes using `defineApiHandler`. Register them on your `app` instance before starting:
+Add server-side routes using `defineApiHandler` or the method helpers (`defineGet`, `definePost`, …). Register them on your `app` instance before starting:
 
 ```typescript
-import { defineApiHandler } from '@ecopages/core';
+import { defineApiHandler, defineGet, json } from '@ecopages/core';
 
-export const helloWorld = defineApiHandler({
+export const helloWorld = defineGet({
 	path: '/api/hello',
-	method: 'GET',
 	handler: async ({ response }) => {
 		return response.json({ message: 'Hello World' });
 	},
 });
+
+// Equivalent with an explicit method:
+export const helloWorldAlt = defineApiHandler({
+	path: '/api/hello',
+	method: 'GET',
+	handler: async () => json({ message: 'Hello World' }),
+});
+```
+
+Group related routes with `defineGroupHandler`. Prefer `api.get` / `api.post` helpers inside the `routes` callback:
+
+```typescript
+import { defineGroupHandler } from '@ecopages/core';
+
+export const adminGroup = defineGroupHandler({
+	prefix: '/admin',
+	routes: (api) => [
+		api.get({
+			path: '/',
+			handler: async ({ response }) => response.json({ ok: true }),
+		}),
+		api.post({
+			path: '/items',
+			handler: async ({ response }) => response.status(201).json({ created: true }),
+		}),
+	],
+});
 ```
 
+Standalone response helpers (`json`, `html`, `redirect`) share the same body emission path as `context.response.json()` / `context.response.html()`.
+
+Register a prebuilt handler with `app.add()`. Use `app.get(path, handler)` only when defining the route inline in `app.ts`.
+
 Attach the handler in your `app.ts` entry:
 
 ```typescript
-// app.ts
 import { createApp } from '@ecopages/core/create-app';
 import { helloWorld } from './handlers/hello';
 import appConfig from './eco.config';
 
 const app = await createApp({ appConfig });
 
-app.get(helloWorld); // Register the API handler
+app.add(helloWorld);
 
 await app.start();
 ```
@@ -223,11 +254,11 @@ Use the `create-app` subpath for runtime startup and the root package for standa
 
 ```ts
 import { createApp } from '@ecopages/core/create-app';
-import { defineApiHandler, defineGroupHandler, eco } from '@ecopages/core';
+import { defineApiHandler, defineGet, defineGroupHandler, eco } from '@ecopages/core';
 ```
 
 > [!NOTE]
-> `createApp` is the recommended entrypoint over `EcopagesApp`.
+> Use `createApp()` from `@ecopages/core/create-app` as the application entrypoint.
 
 ### Runtime Escape Hatches
 
@@ -247,7 +278,6 @@ Use these entrypoints when building an Ecopages app:
 - `@ecopages/core/create-app`
 - `@ecopages/core/config-builder`
 - `@ecopages/core/errors`
-- `@ecopages/core/html`
 - `@ecopages/core/hash`
 - `@ecopages/core/declarations`
 - `@ecopages/core/env`
@@ -267,10 +297,9 @@ Use these entrypoints when implementing integrations, processors, or source tran
 - `@ecopages/core/plugins/integration-plugin`
 - `@ecopages/core/plugins/processor`
 - `@ecopages/core/plugins/source-transform`
-- `@ecopages/core/route-renderer/integration-renderer`
+- `@ecopages/core/route-renderer/orchestration/integration-renderer`
 - `@ecopages/core/services/asset-processing-service`
 - `@ecopages/core/hmr/hmr-strategy`
-- `@ecopages/core/integrations/ghtml`
 
 ### Host And Runtime Composition