@reticlehq/vite-plugin 2.5.0 → 2.7.0

package/dist/index.d.ts

@@ -95,9 +95,9 @@ export interface ReticleVitePlugin {
     config?: (config: {
         optimizeDeps?: {
             include?: string[];
-            esbuildOptions?: {
-                define?: Record<string, string>;
-            };
+            /** Whichever key the app used — the plugin reads both and writes the one this Vite wants. */
+            esbuildOptions?: Record<string, unknown>;
+            rolldownOptions?: Record<string, unknown>;
         };
         define?: Record<string, string>;
         root?: string;
@@ -123,11 +123,28 @@ export interface ReticleVitePlugin {
         root?: string;
         command?: string;
     }) => void;
+    /** Dev-server hook: keeps the served connect module from outliving the token it was built without. */
+    configureServer?: (server: ViteDevServerLike) => void;
     /** Build-time post-condition: desktop injection must have happened. */
     buildEnd?: () => void;
     /** Runs the dev-mode injection check immediately. Test seam for the deferred timer. */
     checkInjectedForTest?: () => void;
 }
+/**
+ * The slice of Vite's dev server this plugin touches, structurally — so `vite` stays a peer the
+ * plugin never imports, the same way the Svelte compiler and Playwright are handled elsewhere.
+ */
+export interface ViteDevServerLike {
+    middlewares: {
+        use(handler: (req: {
+            url?: string | undefined;
+        }, res: unknown, next: () => void) => void): void;
+    };
+    moduleGraph: {
+        getModuleById(id: string): object | undefined;
+        invalidateModule(mod: object): void;
+    };
+}
 interface HtmlTag {
     tag: string;
     /** Absent on an inline script, which carries its source in `children` instead. */

package/dist/index.js

@@ -9,7 +9,7 @@ import { RETICLE_DEFAULT_PORT, RETICLE_RENDER_PREHOOK, bridgeWsUrl, ReticleDir,
 import { resolveProjectId } from './project-id.js';
 import { discoverDaemonPort } from './discover-port.js';
 import { SVELTE_FILE, stampSvelte } from './svelte-source.js';
-import { resolvableChain, sdkPackageVersion, sdkBuildFingerprint, viteMajor, optimizerOptionsKey, } from './installed.js';
+import { resolvableChain, sdkPackageVersion, sdkBuildFingerprint, viteMajor, optimizerOptionsKey, optimizerOptions, } from './installed.js';
 export const RETICLE_VITE_PLUGIN_NAME = 'reticle';
 // The React kit the host app imports the SDK from. It re-exports the browser sensor, so a single
 // specifier yields both `reticle` (connect) and `install` (the React adapter). NOT `@reticlehq/core`
@@ -367,6 +367,7 @@ export function reticle(options = {}) {
             // Everything below asks what the APP has installed, so every lookup is rooted here and never
             // at the plugin's own location. Vite defaults an omitted root to the cwd; so do we.
             const appRoot = config.root ?? process.cwd();
+            const optimizerKey = optimizerOptionsKey(viteMajor(appRoot));
             return {
                 // Expose the daemon's pairing token to hand-written connects in the same Vite app. The
                 // plugin's own injected connect gets the token directly, but a connect the USER writes —
@@ -391,13 +392,12 @@ export function reticle(options = {}) {
                     // Under the key THIS Vite wants. Vite 7 moved the optimizer to rolldown and deprecated
                     // `esbuildOptions`, warning on every boot — a warning attributed to the plugin that set
                     // it, which is us.
-                    [optimizerOptionsKey(viteMajor(appRoot))]: {
+                    // Inherited from whichever key the app used, and `define` placed where this bundler will
+                    // take it — rolldown refuses it at the top level. See optimizerOptions.
+                    [optimizerKey]: optimizerOptions(optimizerKey, {
                         ...(config.optimizeDeps?.esbuildOptions ?? {}),
-                        define: {
-                            ...(config.optimizeDeps?.esbuildOptions?.define ?? {}),
-                            __RETICLE_SDK_BUILD__: JSON.stringify(sdkBuildFingerprint(appRoot)),
-                        },
-                    },
+                        ...(config.optimizeDeps?.rolldownOptions ?? {}),
+                    }, { __RETICLE_SDK_BUILD__: JSON.stringify(sdkBuildFingerprint(appRoot)) }),
                     include: [
                         ...(config.optimizeDeps?.include ?? []),
                         // The SDK ITSELF. Without this, Vite does not learn about @reticlehq/react until the
@@ -463,6 +463,33 @@ export function reticle(options = {}) {
             root = config.root;
             command = config.command;
         },
+        /**
+         * Serve the connect module fresh, every time.
+         *
+         * `load` reads the daemon's pairing token at serve time precisely because the daemon may start
+         * after the dev server — but Vite caches the module it produced, and answers every later request
+         * from that cache, INCLUDING after a full page reload. So a dev server started first served a
+         * tokenless connect module once and then kept serving it: the SDK got a 1008 `authentication
+         * failed`, stopped retrying (correctly — a wrong token does not fix itself), and `reticle status`
+         * showed no session while the page demonstrably contained `/@reticle-connect`. Only restarting
+         * the dev server cleared it, which is not a step anybody guesses.
+         *
+         * Dropping the cached module before it is served makes `load` re-read the token, so starting the
+         * daemon and reloading the page is enough. Costs one string compare per request and re-runs a
+         * three-line module — no reason to be cleverer about when to invalidate.
+         */
+        configureServer(server) {
+            if (!inject)
+                return;
+            server.middlewares.use((req, _res, next) => {
+                if ((req.url ?? '').split('?')[0] === RETICLE_CONNECT_MODULE) {
+                    const mod = server.moduleGraph.getModuleById(RETICLE_CONNECT_MODULE);
+                    if (mod !== undefined)
+                        server.moduleGraph.invalidateModule(mod);
+                }
+                next();
+            });
+        },
         /**
          * Desktop injection is silent when it misses — the bundle simply has no connect() in it and the
          * app looks wired while reporting nothing. That happened twice while this was being built. A

package/dist/installed.d.ts

@@ -68,3 +68,21 @@ export type OptimizerOptionsKey = (typeof OPTIMIZER_OPTIONS_KEY)[keyof typeof OP
  * than an option the installed Vite has never heard of.
  */
 export declare function optimizerOptionsKey(major: number | null): OptimizerOptionsKey;
+/**
+ * The optimizer options object, with `define` where THIS bundler will accept it.
+ *
+ * esbuild reads `define` from the top level of its options. Rolldown does not — it rejects the key
+ * outright and reads defines from `transform.define` instead. Vite 8 surfaces that as a warning on
+ * every dev boot, attributed to whichever plugin set the option:
+ *
+ *   Warning: Invalid input options (1 issue found)
+ *   - For the "define". Invalid key: Expected never but received "define".
+ *
+ * The app still ran, which is why this survived: the option was dropped, `__RETICLE_SDK_BUILD__`
+ * stopped participating in the optimizer cache key, and the only visible symptom was a warning with
+ * Reticle's name on it. Reported by a user on vite@8.0.16.
+ *
+ * An inherited top-level `define` is MOVED rather than dropped on the rolldown path — it is the
+ * app's own, it meant something, and passing it through unchanged is what produced the warning.
+ */
+export declare function optimizerOptions(key: OptimizerOptionsKey, inherited: Record<string, unknown>, add: Record<string, string>): Record<string, unknown>;

package/dist/installed.js

@@ -182,3 +182,33 @@ export function optimizerOptionsKey(major) {
         ? OPTIMIZER_OPTIONS_KEY.ROLLDOWN
         : OPTIMIZER_OPTIONS_KEY.ESBUILD;
 }
+/**
+ * The optimizer options object, with `define` where THIS bundler will accept it.
+ *
+ * esbuild reads `define` from the top level of its options. Rolldown does not — it rejects the key
+ * outright and reads defines from `transform.define` instead. Vite 8 surfaces that as a warning on
+ * every dev boot, attributed to whichever plugin set the option:
+ *
+ *   Warning: Invalid input options (1 issue found)
+ *   - For the "define". Invalid key: Expected never but received "define".
+ *
+ * The app still ran, which is why this survived: the option was dropped, `__RETICLE_SDK_BUILD__`
+ * stopped participating in the optimizer cache key, and the only visible symptom was a warning with
+ * Reticle's name on it. Reported by a user on vite@8.0.16.
+ *
+ * An inherited top-level `define` is MOVED rather than dropped on the rolldown path — it is the
+ * app's own, it meant something, and passing it through unchanged is what produced the warning.
+ */
+export function optimizerOptions(key, inherited, add) {
+    const inheritedDefine = (inherited['define'] ?? {});
+    if (OPTIMIZER_OPTIONS_KEY.ROLLDOWN !== key) {
+        return { ...inherited, define: { ...inheritedDefine, ...add } };
+    }
+    const { define: _moved, ...rest } = inherited;
+    const transform = (inherited['transform'] ?? {});
+    const transformDefine = (transform['define'] ?? {});
+    return {
+        ...rest,
+        transform: { ...transform, define: { ...inheritedDefine, ...transformDefine, ...add } },
+    };
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reticlehq/vite-plugin",
-  "version": "2.5.0",
+  "version": "2.7.0",
   "description": "Vite plugin for Reticle: dev-only source-map stamping plus auto-injected reticle.connect(). apply:'serve' guarantees it never ships to production.",
   "type": "module",
   "license": "Apache-2.0",
@@ -35,8 +35,8 @@
   ],
   "dependencies": {
     "@babel/core": "^7.26.0",
-    "@reticlehq/babel-plugin": "2.5.0",
-    "@reticlehq/core": "2.5.0"
+    "@reticlehq/babel-plugin": "2.7.0",
+    "@reticlehq/core": "2.7.0"
   },
   "devDependencies": {
     "@types/babel__core": "^7.20.5",