vite-plugin-rebundle 1.2.5 → 1.2.6

package/dist/rebundle.js

@@ -140,7 +140,7 @@ export class Rebundle extends $utils.Unit {
             await this.removeDirectoryIfEmpty(dir);
         }
         // Notify about changed chunks
-        if (changedChunkNames.length > 0) {
+        if (ws && changedChunkNames.length > 0) {
             ws.clients.forEach(client => client.send(JSON.stringify(changedChunkNames)));
         }
     };
@@ -166,6 +166,10 @@ export class Rebundle extends $utils.Unit {
             return this.ws;
         if (!this.port)
             throw this.never;
+        if (!this.config)
+            throw this.never;
+        if (!this.config.build.watch)
+            return null;
         this.ws = new $ws.WebSocketServer({ port: this.port });
         return this.ws;
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vite-plugin-rebundle",
-  "version": "1.2.5",
+  "version": "1.2.6",
   "type": "module",
   "license": "MIT",
   "author": "imkost",

package/readme.md

@@ -6,8 +6,6 @@ A Vite plugin that guarantees **one standalone file per entry point**. Each entr
 
 Sometimes you need bundles without dynamic imports. Vite/Rollup don’t provide this option when building with multiple entries. This plugin solves it by rebundling Vite’s output with esbuild to enforce single-file output.
 
-> ℹ️ Useful when targeting environments that require standalone files (e.g., browser extensions, legacy systems, or file-based distribution).
-
 > ⚠️ This plugin runs **only during** `vite build`. It does not affect the Vite dev server.
 
 ## Installation
@@ -38,7 +36,7 @@ export default defineConfig({
 })
 ```
 
-### Options
+## Options
 
 You can provide **esbuild options per entry point**. This is useful, for example, to inject custom define variables into specific bundles: