@fougere/admin 0.13.0-alpha.0 → 0.14.0-alpha.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fougere/admin",
-  "version": "0.13.0-alpha.0",
+  "version": "0.14.0-alpha.0",
   "description": "A back-office derived from what the app already says it hosts — a react-admin DataProvider over the Fougere wire.",
   "keywords": [
     "fougere",
@@ -36,9 +36,9 @@
   ],
   "dependencies": {
     "@dagrejs/dagre": "^3.1.1",
-    "@fougere/app": "0.13.0-alpha.0",
-    "@fougere/core": "0.13.0-alpha.0",
-    "@fougere/schema": "0.13.0-alpha.0"
+    "@fougere/app": "0.14.0-alpha.0",
+    "@fougere/core": "0.14.0-alpha.0",
+    "@fougere/schema": "0.14.0-alpha.0"
   },
   "devDependencies": {
     "@mui/material": "^9.3.1",

package/template/package.json

@@ -14,6 +14,7 @@
     "react-dom": "^19.0.0"
   },
   "devDependencies": {
+    "@fougere/vite": "latest",
     "@types/react": "^19.0.0",
     "@types/react-dom": "^19.0.0",
     "@vitejs/plugin-react": "^5.0.0",

package/template/src/main.tsx

@@ -10,8 +10,8 @@ import { createRoot } from 'react-dom/client';
 import { FougereAdmin } from '@fougere/admin/react';
 
 /**
- * No `endpoint`, so it stays `/_fougere/call` — a relative address the dev proxy in
- * `vite.config.ts` forwards to the app next door.
+ * No `endpoint`, so it stays `/_fougere/call` — the dev server answers there itself, through
+ * `fougere()` in `vite.config.ts`.
  *
  * The integrated shape is the same component with nothing changed at all: mount it on a route
  * of the app that serves the frond, and same-origin does the rest. Standalone against another

package/template/vite.config.ts

@@ -1,16 +1,13 @@
 import { defineConfig } from 'vite';
+import { fougere } from '@fougere/vite';
 import react from '@vitejs/plugin-react';
 
 /**
- * No `@fougere/vite` here: this app scans nothing and boots nothing. It is a reader of one
- * endpoint, and the only thing it needs is a way to reach it without crossing an origin.
- *
- * Point the proxy at whichever app serves your frond. In production the two are usually
- * behind one host, and this block goes away.
+ * The admin reads the identity card at `/_fougere/call`, and `fougere()` answers there: the dev
+ * server boots the app from `fougere.config.ts`, so `fronds:` decides whether a frond answers in
+ * this process or a process away.
  */
 export default defineConfig({
-  plugins: [react()],
-  server: {
-    proxy: { '/_fougere': 'http://localhost:3000' },
-  },
+  // Fronds are shared at the workspace root, two levels up from apps/<name>.
+  plugins: [fougere({ root: '../..' }), react()],
 });