vite-plugin-smart-prefetch 0.3.1 → 0.3.3

package/dist/index.js

@@ -698,21 +698,14 @@ var _ConfigGenerator = class _ConfigGenerator {
       }
       prediction.prefetch.forEach((target) => {
         const chunkFile = this.routeToChunk(target.route);
+        let imports = [];
         if (chunkFile) {
           const manifestEntry = this.getManifestEntryByFile(chunkFile);
           const importChunkIds = manifestEntry?.imports || [];
-          const imports = importChunkIds.map((chunkId) => {
+          imports = importChunkIds.map((chunkId) => {
             const entry = this.manifest[chunkId];
             return entry?.file;
           }).filter((file) => !!file);
-          prefetchTargets.push({
-            ...target,
-            chunk: chunkFile,
-            chunk_prod: chunkFile,
-            // NEW: Include production chunk path
-            imports
-            // Include dependency chunks (resolved to file paths)
-          });
           config.chunks[target.route] = chunkFile;
           mappedRoutes++;
           if (this.debug) {
@@ -729,29 +722,39 @@ var _ConfigGenerator = class _ConfigGenerator {
           }
           unmappedRoutes++;
         }
+        prefetchTargets.push({
+          ...target,
+          chunk: chunkFile || void 0,
+          // Include chunk (may be undefined)
+          chunk_prod: chunkFile || void 0,
+          // Include production chunk path
+          imports
+        });
       });
       if (prediction.segments) {
         Object.entries(prediction.segments).forEach(([segment, segmentTargets]) => {
           const segmentPrefetchTargets = [];
           segmentTargets.forEach((target) => {
             const chunkFile = this.routeToChunk(target.route);
+            let imports = [];
             if (chunkFile) {
               const manifestEntry = this.getManifestEntryByFile(chunkFile);
               const importChunkIds = manifestEntry?.imports || [];
-              const imports = importChunkIds.map((chunkId) => {
+              imports = importChunkIds.map((chunkId) => {
                 const entry = this.manifest[chunkId];
                 return entry?.file;
               }).filter((file) => !!file);
-              segmentPrefetchTargets.push({
-                ...target,
-                chunk: chunkFile,
-                chunk_prod: chunkFile,
-                // NEW: Include production chunk path
-                imports
-              });
               config.chunks[target.route] = chunkFile;
               totalSegmentRules++;
             }
+            segmentPrefetchTargets.push({
+              ...target,
+              chunk: chunkFile || void 0,
+              // Include chunk (may be undefined)
+              chunk_prod: chunkFile || void 0,
+              // Include production chunk path
+              imports
+            });
           });
           if (segmentPrefetchTargets.length > 0) {
             segmentConfigs[segment] = segmentPrefetchTargets;
@@ -1170,9 +1173,23 @@ var _ConfigGenerator = class _ConfigGenerator {
 };
 /**
  * Maps routes to their component names based on vite.config.ts chunk strategy
- * This is derived from the route configuration in src/routes/index.ts
- * Note: These are the core routes from vite.config.ts chunking strategy
- * Routes not listed here will fall through to fuzzy matching
+ *
+ * ⚠️  HARDCODED MAPPINGS ARE NOT RECOMMENDED FOR PRODUCTION
+ *
+ * These mappings should NOT be hardcoded in the plugin.
+ * Instead, implement one of these approaches:
+ *
+ * 1. **Extract from Vite Config (RECOMMENDED)**:
+ *    Pass route-to-chunk mappings from your vite.config.ts manualChunks strategy
+ *    This keeps mappings DRY and maintainable.
+ *
+ * 2. **Generate from Route Files**:
+ *    Scan your routes/pages directory to dynamically build mappings
+ *
+ * 3. **Use Route Metadata**:
+ *    Add metadata to route definitions specifying their chunk names
+ *
+ * Current hardcoded mappings (will be removed in v0.4.0):
  */
 _ConfigGenerator.ROUTE_TO_COMPONENT_NAME = {
   "/": "Home",
@@ -1208,10 +1225,16 @@ _ConfigGenerator.ROUTE_TO_COMPONENT_NAME = {
 };
 /**
  * Maps component names to chunk names based on vite.config.ts manualChunks strategy
- * Each component is assigned to a specific chunk group for code splitting
+ *
+ * ⚠️  HARDCODED MAPPINGS ARE NOT RECOMMENDED FOR PRODUCTION
+ *
+ * Each component is assigned to a specific chunk group for code splitting.
+ * These mappings should be extracted from your actual vite.config.ts, not hardcoded.
  *
  * Note: Core components (Home, Dashboard) are not in manual chunks - they're part of main bundle
  * For these, we return the main bundle file path 'js/index-*.js' which will be resolved from manifest
+ *
+ * Will be removed in v0.4.0. Use plugin config to pass mappings instead.
  */
 _ConfigGenerator.COMPONENT_TO_CHUNK_NAME = {
   // Core components - loaded with main bundle (not code-split)