@vercube/vite 1.1.7 → 1.2.0

package/README.md

@@ -83,9 +83,9 @@ node dist/index.mjs   # runs the built server
 
 ### `noExternal`
 
-Vercube keeps `@vercube/*` in a single module graph so class-reference DI tokens are not loaded twice. If a dependency imports `@vercube/core` from its published `dist` while your app resolves a different copy (common with pnpm), inject tokens such as `RequestContext` will not match — auth middleware writes to one instance, your services read from another.
+Vercube keeps `@vercube/*` in a single module graph so class-reference DI tokens are not loaded twice. If a dependency imports `@vercube/core` from its published `dist` while your app resolves a different copy (common with pnpm), inject tokens such as `RequestContext` will not match - auth middleware writes to one instance, your services read from another.
 
-The same patterns apply in **dev** (`resolve.noExternal`). In **production** the server bundle keeps `@vercube/*` and plugin packages as runtime imports — only app source (`@/…`) is inlined. Use **one** `@vercube/core` version across the app and dependencies (e.g. pnpm `overrides`), otherwise class-reference DI tokens such as `RequestContext` will not match between `@enp/auth` and your services.
+The same patterns apply in **dev** (`resolve.noExternal`). In **production** the server bundle keeps `@vercube/*` and plugin packages as runtime imports - only app source (`@/…`) is inlined. Use **one** `@vercube/core` version across the app and dependencies (e.g. pnpm `overrides`), otherwise class-reference DI tokens such as `RequestContext` will not match between `@enp/auth` and your services.
 
 Add packages that use Vercube DI tokens:
 

package/dist/index.d.mts

@@ -22,7 +22,7 @@ interface VercubePluginConfig {
   /**
    * Path (relative to `rootDir`) to a module whose default export is
    * `(app: App) => void | Promise<void>`. Runs after auto-discovered classes are
-   * bound but before the container queue is flushed — use it to mount storage,
+   * bound but before the container queue is flushed - use it to mount storage,
    * bind tokens, configure the logger, or register plugins that auto-discovery
    * cannot infer.
    */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vercube/vite",
-  "version": "1.1.7",
+  "version": "1.2.0",
   "description": "Vite plugin integrating Vercube with the Vite Environment API",
   "repository": {
     "type": "git",
@@ -34,15 +34,15 @@
     "defu": "6.1.7",
     "env-runner": "0.1.16",
     "pathe": "2.0.3",
-    "rou3": "0.9.1",
-    "srvx": "0.11.22",
-    "@vercube/scan": "1.1.7"
+    "rou3": "0.9.2",
+    "srvx": "0.12.5",
+    "@vercube/scan": "1.2.0"
   },
   "peerDependencies": {
     "vite": "^8.0.0"
   },
   "devDependencies": {
-    "vite": "^8.1.5"
+    "vite": "^8.2.1"
   },
   "publishConfig": {
     "access": "public"