tonka-vite-plugin 1.21.0 → 1.31.0

package/README.md

@@ -14,10 +14,9 @@ This plugin automates the configuration of Vite for applications using **Inertia
 
 ## 📦 Installation
 
-Since this is a local plugin specific to your Tonka setup, copy the plugin file into your project root.
-
-1.  Create a file named `tonka-vite-plugin.ts` (or `.js`) in your project root.
-2.  Paste the code provided in the documentation into this file.
+```bash
+npm i tonka-vite-plugin
+```
 
 ## 🚀 Quick Start
 
@@ -26,7 +25,7 @@ Import the plugin into your `vite.config.ts` to activate it.
 ```typescript
 import { defineConfig } from 'vite';
 import react from '@vitejs/plugin-react';
-import tonka from './tonka-vite-plugin';
+import tonka from 'tonka-vite-plugin';
 
 export default defineConfig({
   plugins: [
@@ -68,14 +67,14 @@ When you run `npm run build`, the plugin automatically configures Rollup (the bu
 If you provide an `ssr` entry point, the plugin configures Vite to perform a second build specifically for the server. This allows your backend (Tonka) to render the initial page state on the server for faster load times and SEO.
 
 ### 3. Integration with Backend
-The plugin prepares the assets, but the **injection** of the `<script>` tags into the HTML is handled by your backend (Tonka) via the `@vite` Blade directive. This ensures that the correct script source is used:
+The plugin prepares the assets, but the **injection** of the `<script>` tags into the HTML is handled by your backend (Tonka) via the `@vite` directive. This ensures that the correct script source is used:
 *   **Dev**: Points to `http://localhost:5173/@vite/client` (for HMR).
 *   **Prod**: Points to `/build/assets/xxxxx.js` (using the manifest).
 
 ## 🛠️ Development vs Production
 
 **In Development:**
-The plugin ensures the dev server runs on port 5173 and resolves aliases correctly. It relies on the backend to proxy requests or inject the client script.
+The plugin ensures the dev server runs on port `5173` (or the one you specify for vite) and resolves aliases correctly. It relies on the backend to proxy requests or inject the client script.
 
 **In Production:**
 The plugin is essential to correctly generate the `manifest.json`. Without this plugin generating the manifest, your backend would fail to locate the compiled `.js` files after a build.

package/dist/index.d.ts

@@ -0,0 +1,3 @@
+import type { Plugin } from 'vite';
+import { TonkaPluginOptions } from '../types';
+export default function tonkaPlugin(options?: TonkaPluginOptions): Plugin;

package/dist/index.js

@@ -0,0 +1,42 @@
+import path from 'path';
+export default function tonkaPlugin(options = {}) {
+    const root = process.cwd();
+    return {
+        name: 'tonka-vite-plugin',
+        config: (userConfig, { command }) => {
+            const input = options.input || {
+                'resources/css/app.css': undefined,
+                'resources/js/app.tsx': undefined,
+            };
+            const outDir = options.outDir || path.resolve(root, 'public/build');
+            const manifest = options.manifest !== false ? 'manifest.json' : false;
+            const ssrBuild = options.ssr ? options.ssr : false;
+            return {
+                build: {
+                    outDir: outDir,
+                    manifest: manifest,
+                    assetsDir: options.assetsDir || 'assets',
+                    rollupOptions: {
+                        input: input,
+                    },
+                    ssr: ssrBuild,
+                    sourcemap: command === 'serve',
+                },
+                resolve: {
+                    alias: options.alias || {
+                        '@': path.resolve(root, '.'),
+                    },
+                },
+                optimizeDeps: {
+                    include: ['react', 'react-dom', '@inertiajs/react', 'axios'],
+                    exclude: [],
+                },
+            };
+        },
+        transformIndexHtml(html) {
+            if (options.refresh) {
+            }
+            return html;
+        },
+    };
+}

package/package.json

@@ -1,10 +1,22 @@
 {
   "name": "tonka-vite-plugin",
-  "version": "1.21.0",
+  "version": "1.31.0",
   "description": "A Vite plugin for Inertia.js that provides automatic page imports and enhanced development experience.",
-  "main": "index.ts",
+  "main": "./dist/index.js",       
+  "types": "./dist/index.d.ts",     
+  "exports": {
+    ".": "./dist/index.js"
+  },
+  "files": [
+    "dist",
+    "types"
+  ],
   "scripts": {
-    "test": "echo \"Error: no test specified\" && exit 1"
+    "build": "tsc" 
+  },
+  "devDependencies": {
+    "typescript": "^5.0.0",
+    "vite": "^5.0.0" 
   },
   "repository": {
     "type": "git",

package/bin/index.ts

@@ -1,101 +0,0 @@
-import type { Plugin, UserConfig } from 'vite';
-import { fileURLToPath, URL } from 'node:url';
-import path from 'path';
-import { TonkaPluginOptions } from '../lib';
-
-/**
- * Tonka Vite Plugin
- * 
- * A Vite plugin specifically designed for the Tonka Framework.
- * It automates the configuration for Inertia.js, SSR, and asset paths.
- * 
- * @param options - Configuration options for the plugin
- * @returns A Vite plugin object
- */
-export default function tonkaPlugin(options: TonkaPluginOptions = {}): Plugin {
-  // Determine the base directory of the project
-  const root = process.cwd();
-
-  return {
-    name: 'tonka-vite-plugin',
-
-    /**
-     * The `config` hook is called before the user config is resolved.
-     * We use it to inject default settings and handle the Tonka-specific structure.
-     */
-    config: (userConfig: UserConfig, { command }) => {
-      // 1. Handle Inputs
-      // If the user doesn't provide inputs, we assume the standard structure.
-      // Note: We cast to 'any' here to satisfy Rollup's strict typing for input.
-      const input: any = options.input || {
-        'resources/css/app.css': undefined, // CSS entry
-        'resources/js/app.tsx': undefined,   // Main JS entry
-      };
-
-      // 2. Handle Output Directory
-      // Default to 'public/build' if not specified
-      const outDir = options.outDir || path.resolve(root, 'public/build');
-
-      // 3. Handle Manifest
-      // Ensure manifest is generated unless explicitly disabled
-      const manifest = options.manifest !== false ? 'manifest.json' : false;
-
-      // 4. Handle SSR
-      // If ssr is false, we ensure we don't set the ssr config.
-      const ssrBuild = options.ssr ? options.ssr : false;
-
-      return {
-        build: {
-          outDir: outDir,
-          manifest: manifest,
-          assetsDir: options.assetsDir || 'assets',
-          
-          // Rollup options
-          rollupOptions: {
-            input: input,
-          },
-          
-          // Server-Side Rendering configuration
-          ssr: ssrBuild,
-          
-          // Source maps: enabled in dev, disabled in prod (optional optimization)
-          sourcemap: command === 'serve',
-        },
-
-        // 5. Resolve Aliases
-        resolve: {
-          // Merge user aliases with defaults
-          alias: options.alias || {
-            // Default alias: '@' points to the root of the project
-            // You can also point it to 'resources' or 'public' based on your preference.
-            '@': path.resolve(root, '.'),
-          },
-        },
-
-        // 6. Optimize dependencies
-        // Pre-bundle common dependencies to speed up dev server start
-        optimizeDeps: {
-          include: ['react', 'react-dom', '@inertiajs/react', 'axios'],
-          exclude: [],
-        },
-      };
-    },
-
-    /**
-     * The `transformIndexHtml` hook allows modifying the HTML index file.
-     * This can be used to inject the @vite/client script for HMR if needed.
-     */
-    transformIndexHtml(html) {
-      // If refresh is enabled, we could inject the HMR client here.
-      // However, in a typical Inertia setup (like Tonka), this is often
-      // handled by the server-side Blade/PHP template (@vite directive).
-      // We leave this placeholder for future enhancements.
-      if (options.refresh) {
-        // Implementation note: Injecting @vite/client usually requires
-        // knowing the exact module path, which varies. 
-        // For now, we trust the server-side directive.
-      }
-      return html;
-    },
-  };
-}

package/index.ts

@@ -1,2 +0,0 @@
-import tonkaPlugin from './bin';
-export default tonkaPlugin;