@rebasepro/app 0.19.2-canary.gef769df → 0.20.0

package/dist/vitePlugin.d.ts

@@ -1,4 +1,5 @@
 import MagicString from "magic-string";
+import type { Plugin } from "vite";
 export interface RebaseCollectionsPluginOptions {
     /**
      * The path to the collections directory containing the schema definitions.
@@ -33,31 +34,22 @@ export declare function transformCollectionSource(code: string, id: string): {
  *    (`{ __rebaseLazy: true, load: () => import(...) }`), enabling code-splitting
  *    and preventing the backend from loading React-dependent modules.
  */
-export declare function rebaseCollectionsPlugin(options: RebaseCollectionsPluginOptions): {
-    name: string;
-    configResolved(config: {
-        root: string;
-    }): void;
-    resolveId(id: string): string | null;
-    load(id: string): string | null;
-    /**
-     * Transform collection files to convert string component references
-     * into lazy-loading `LazyComponentRef` objects.
-     *
-     * Example transform:
-     * ```
-     * // Input
-     * Field: "../../frontend/src/components/MyField"
-     *
-     * // Output
-     * Field: { __rebaseLazy: true, load: () => import("../../frontend/src/components/MyField") }
-     * ```
-     */
-    transform(code: string, id: string): {
-        code: string;
-        map: ReturnType<MagicString["generateMap"]>;
-    } | null;
-};
+/**
+ * Annotated `Plugin` rather than inferred.
+ *
+ * The return used to be a bare object literal, and TypeScript 6 stopped
+ * accepting it where vite wants a `PluginOption`: `configureServer` is an
+ * `ObjectHook`, so a plain method's inferred signature is not assignable, and
+ * the whole config object then failed with "Excessive stack depth comparing
+ * types" — an error naming the caller's `defineConfig` rather than the plugin
+ * that caused it. A scaffolded frontend runs `vite build && tsc` with
+ * `vite.config.ts` in its `include`, so that was a broken `pnpm build` for
+ * every new project on TS 6, reported against a file the user did not write.
+ *
+ * Declaring the type puts the check here, where the hooks are, instead of at
+ * every call site.
+ */
+export declare function rebaseCollectionsPlugin(options: RebaseCollectionsPluginOptions): Plugin;
 /**
  * How the admin's dependencies are split into cached chunks.
  *

package/dist/vitePlugin.js

@@ -66,6 +66,35 @@ function rebaseCollectionsPlugin(options) {
     configResolved(config) {
       resolvedCollectionsDir = path.isAbsolute(options.collectionsDir) ? options.collectionsDir : path.resolve(config.root, options.collectionsDir);
     },
+    /**
+     * Watch the collections directory itself, not just the files in it.
+     *
+     * The virtual module below is an `import.meta.glob`, and Vite already
+     * invalidates a glob's importer when a matching file appears — but only
+     * for files its watcher sees. The watcher watches the Vite root, plus
+     * whatever individual files the module graph reached; a collections
+     * directory outside the root (`collectionsDir: "../config/collections"`
+     * is the shape every scaffold ships) is therefore watched one existing
+     * file at a time, and a *new* file in it raises no event at all.
+     *
+     * That is the whole of the "created a collection, it is in the source,
+     * it is not in the admin" bug: the editor wrote the file, nothing
+     * invalidated the virtual module, and the collection list stayed
+     * whatever it was when the dev server booted — a reload did not fix it,
+     * because the stale glob was already transformed and cached. Only a
+     * restart did.
+     *
+     * Editing an existing collection was always fine, which is why this hid
+     * for so long: that file IS in the module graph, so it IS watched.
+     *
+     * Watching the directory is the whole fix. Vite's own glob invalidation
+     * does the rest — it is listening on this same watcher, and once the
+     * event reaches it, it invalidates the virtual module and reloads the
+     * page exactly as it does for a collections directory inside the root.
+     */
+    configureServer(server) {
+      server.watcher.add(resolvedCollectionsDir);
+    },
     resolveId(id) {
       if (id === virtualModuleId) {
         return resolvedVirtualModuleId;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rebasepro/app",
-  "version": "0.19.2-canary.gef769df",
+  "version": "0.20.0",
   "description": "Rebase core — framework-agnostic runtime for data-driven admin panels",
   "keywords": [
     "rebase",
@@ -63,12 +63,12 @@
     "magic-string": "^0.30.0",
     "notistack": "^3.0.2",
     "react-i18next": "^17.0.11",
-    "@rebasepro/cms-types": "0.19.2-canary.gef769df",
-    "@rebasepro/common": "0.19.2-canary.gef769df",
-    "@rebasepro/forms": "0.19.2-canary.gef769df",
-    "@rebasepro/ui": "0.19.2-canary.gef769df",
-    "@rebasepro/types": "0.19.2-canary.gef769df",
-    "@rebasepro/utils": "0.19.2-canary.gef769df"
+    "@rebasepro/cms-types": "0.20.0",
+    "@rebasepro/common": "0.20.0",
+    "@rebasepro/forms": "0.20.0",
+    "@rebasepro/ui": "0.20.0",
+    "@rebasepro/types": "0.20.0",
+    "@rebasepro/utils": "0.20.0"
   },
   "peerDependencies": {
     "react": "^19.2.7",