@kbach/react 0.6.6 → 0.6.7

package/README.md

@@ -73,6 +73,8 @@ export default defineConfig({
 });
 ```
 
+Adding the plugin also declares `@kbach/react` in Vite's `optimizeDeps.include` upfront, so Vite pre-bundles it during its initial dependency scan instead of discovering it lazily on the first page that imports it — avoiding a forced full-reload mid-render, which is what a rare "Invalid hook call"-style crash on first load (but never again after) usually turns out to be.
+
 Then create an empty `kbach.css` anywhere in your project and import it once in your app entry:
 
 ```css

package/dist/vite-plugin.js

@@ -3360,6 +3360,21 @@ function kbach(userConfigOrOptions) {
   return {
     name: "kbach",
     enforce: "pre",
+    // Without this, Vite only discovers @kbach/react needs pre-bundling once it
+    // actually crawls into an import of it — typically the FIRST page load — and
+    // has to stop, optimize it, and force a full reload mid-render. That reload
+    // can land in the middle of a render pass (React hooks resolving against a
+    // module graph that's being swapped out from under it), which is what an
+    // "Invalid hook call" / hook-related crash on first load only usually is.
+    // Declaring it here upfront means Vite pre-bundles it during its initial
+    // dependency scan, before any page ever requests it — no mid-render reload.
+    config() {
+      return {
+        optimizeDeps: {
+          include: ["@kbach/react", "@kbach/react/jsx-runtime", "@kbach/react/jsx-dev-runtime"]
+        }
+      };
+    },
     configResolved(resolved) {
       root = resolved.root;
       const names = new Set(resolved.plugins.map((p) => p.name));

package/dist/vite-plugin.mjs

@@ -3326,6 +3326,21 @@ function kbach(userConfigOrOptions) {
   return {
     name: "kbach",
     enforce: "pre",
+    // Without this, Vite only discovers @kbach/react needs pre-bundling once it
+    // actually crawls into an import of it — typically the FIRST page load — and
+    // has to stop, optimize it, and force a full reload mid-render. That reload
+    // can land in the middle of a render pass (React hooks resolving against a
+    // module graph that's being swapped out from under it), which is what an
+    // "Invalid hook call" / hook-related crash on first load only usually is.
+    // Declaring it here upfront means Vite pre-bundles it during its initial
+    // dependency scan, before any page ever requests it — no mid-render reload.
+    config() {
+      return {
+        optimizeDeps: {
+          include: ["@kbach/react", "@kbach/react/jsx-runtime", "@kbach/react/jsx-dev-runtime"]
+        }
+      };
+    },
     configResolved(resolved) {
       root = resolved.root;
       const names = new Set(resolved.plugins.map((p) => p.name));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kbach/react",
-  "version": "0.6.6",
+  "version": "0.6.7",
   "description": "React / React Native components and hooks for the Kbach framework",
   "source": "./src/index.ts",
   "main": "./dist/index.js",