vike 0.4.246 → 0.4.247

package/dist/esm/node/api/resolveViteConfigFromUser.js

@@ -89,7 +89,7 @@ async function getViteInfo(viteConfigFromUserVikeApiOptions, viteContext) {
         // Show a warning because Vike supports Vite's CLI (as well as third-party CLIs).
         // - Encourage users to define a vite.config.js file that also works with Vite's CLI (and potentially other third-party CLIs).
         // - Vike-based frameworks, such as DocPress, allow their users to omit defining a vite.config.js file.
-        assertWarning(viteConfigFromUserViteConfigFile, // Only show the warning if the user defined a vite.config.js file
+        assertWarning(!viteConfigFromUserViteConfigFile, // Only show the warning if the user defined a vite.config.js file
         "Omitting Vike's Vite plugin (inside your vite.config.js) is deprecated — make sure to always add Vike's Vite plugin https://vike.dev/vite-plugin", { onlyOnce: true });
         // Add Vike to plugins if not present.
         // Using a dynamic import because the script calling the Vike API may not live in the same place as vite.config.js, thus vike/plugin may resolved to two different node_modules/vike directories.

package/dist/esm/node/vite/plugins/pluginDev/determineOptimizeDeps.js

@@ -1,22 +1,46 @@
 export { determineOptimizeDeps };
 import { findPageFiles } from '../../shared/findPageFiles.js';
-import { assert, assertIsImportPathNpmPackage, createDebugger, getNpmPackageName, isArray, isFilePathAbsoluteFilesystem, isVirtualFileId, } from '../../utils.js';
+import { assert, assertIsImportPathNpmPackage, createDebugger, getNpmPackageName, isArray, isFilePathAbsoluteFilesystem, isVirtualFileId, requireResolveOptional, } from '../../utils.js';
 import { getVikeConfigInternal } from '../../shared/resolveVikeConfigInternal.js';
 import { analyzeClientEntries } from '../build/pluginBuildConfig.js';
 import { virtualFileIdGlobalEntryClientCR, virtualFileIdGlobalEntryClientSR } from '../../../shared/virtualFileId.js';
 import { getFilePathResolved } from '../../shared/getFilePath.js';
 import { getConfigValueSourcesRelevant } from '../pluginVirtualFiles/getConfigValueSourcesRelevant.js';
 const debug = createDebugger('vike:optimizeDeps');
+const WORKAROUND_LATE_DISCOVERY = [
+    // Workaround for https://github.com/vitejs/vite-plugin-react/issues/650
+    // - The issue was closed as completed with https://github.com/vitejs/vite/pull/20495 but it doesn't fix the issue and the workaround is still needed.
+    // - TO-DO/eventually: try removing the workaround and see if the CI fails (at test/@cloudflare_vite-plugin/) — maybe the issue will get fixed at some point.
+    'react/jsx-dev-runtime',
+    // Workaround for https://github.com/vikejs/vike/issues/2823#issuecomment-3514325487
+    '@compiled/react/runtime',
+];
 async function determineOptimizeDeps(config) {
     const vikeConfig = await getVikeConfigInternal();
     const { _pageConfigs: pageConfigs } = vikeConfig;
     const { entriesClient, entriesServer, includeClient, includeServer } = await getPageDeps(config, pageConfigs);
+    WORKAROUND_LATE_DISCOVERY.forEach((dep) => {
+        const userRootDir = config.root;
+        const resolved = requireResolveOptional({ importPath: dep, userRootDir, importerFilePath: null });
+        const resolvedInsideRepo = resolved && resolved.startsWith(userRootDir);
+        if (resolvedInsideRepo) {
+            // We add `dep` only if `resolvedInsideRepo === true` otherwise Vite logs a warning like the following.
+            // - ```console
+            //   [11:22:42.464][/examples/vue-full][npm run dev][stderr] Failed to resolve dependency: react/jsx-dev-runtime, present in client 'optimizeDeps.include'
+            //   ```
+            // - ```console
+            //   [12:24:53.225][/test/@cloudflare_vite-plugin/test-dev.test.ts][npm run dev][stderr] Failed to resolve dependency: @compiled/react/runtime, present in ssr 'optimizeDeps.include'
+            //   ```
+            includeClient.push(dep);
+            includeServer.push(dep);
+        }
+        else if (config.optimizeDeps.include?.includes(dep)) {
+            // Monorepo => always `resolvedInsideRepo === false` — we use this other approach to workaround missing 'react/jsx-dev-runtime'
+            includeServer.push(dep);
+        }
+    });
     config.optimizeDeps.include = add(config.optimizeDeps.include, includeClient);
     config.optimizeDeps.entries = add(config.optimizeDeps.entries, entriesClient);
-    // Workaround for https://github.com/vitejs/vite-plugin-react/issues/650
-    // - The issue was closed as completed with https://github.com/vitejs/vite/pull/20495 but it doesn't fix the issue and the workaround is still needed.
-    // - TO-DO/eventually: try removing the workaround and see if the CI fails (at test/@cloudflare_vite-plugin/) — maybe the issue will get fixed at some point.
-    includeServer.push('react/jsx-dev-runtime');
     for (const envName in config.environments) {
         const env = config.environments[envName];
         if (env.consumer === 'server' && env.optimizeDeps.noDiscovery === false) {

package/dist/esm/node/vite/plugins/pluginDev.js

@@ -21,38 +21,21 @@ function pluginDev() {
                 handler() {
                     return {
                         appType: 'custom',
-                        // TO-DO/next-major-release: remove (AFAICT we only need to use config.optimizeDeps for the old design)
                         optimizeDeps: {
                             exclude: [
-                                // We exclude Vike's client runtime to be able to use Vite's import.meta.glob()
+                                // We must exclude Vike's client runtime so it can import virtual modules
                                 'vike/client',
                                 'vike/client/router',
-                                // It seems like client-side/isomorphic imports also need to be excluded, in order to avoid the following:
-                                //   ```
-                                //   Client runtime loaded twice https://vike.dev/client-runtime-duplicated
-                                //   ```
-                                'vike/routing',
-                                'vike/getPageContext',
-                                // We exclude @brillout/json-serializer and @brillout/picocolors to avoid:
+                            ],
+                            include: [
+                                // Avoid:
                                 // ```
                                 // 9:28:58 AM [vite] ✨ new dependencies optimized: @brillout/json-serializer/parse
                                 // 9:28:58 AM [vite] ✨ optimized dependencies changed. reloading
                                 // ```
-                                '@brillout/json-serializer/parse',
-                                '@brillout/json-serializer/stringify',
-                                '@brillout/picocolors',
-                                // We exclude all packages that depend on any optimizeDeps.exclude entry because, otherwise, the entry cannot be resolved when using pnpm. For example:
-                                // ```
-                                // Failed to resolve import "@brillout/json-serializer/parse" from "../../packages/vike-react-query/dist/renderer/VikeReactQueryWrapper.js". Does the file exist?
-                                // 343|  // ../../node_modules/.pnpm/react-streaming@0.3.16_react-dom@18.2.0_react@18.2.0/node_modules/react-streaming/dist/esm/client/useAsync.js
-                                // 344|  import { parse as parse2 } from "@brillout/json-serializer/parse";
-                                // ```
-                                // The source map is confusing, the import actually lives at node_modules/.vite/deps/vike-react-query_renderer_VikeReactQueryWrapper.js which contains:
-                                // ```js
-                                // // ../../node_modules/.pnpm/react-streaming@0.3.16_react-dom@18.2.0_react@18.2.0/node_modules/react-streaming/dist/esm/client/useAsync.js
-                                // import { parse as parse2 } from "@brillout/json-serializer/parse";
-                                // ```
-                                'react-streaming',
+                                'vike > @brillout/json-serializer/parse',
+                                'vike > @brillout/json-serializer/stringify',
+                                'vike > @brillout/picocolors',
                             ],
                         },
                     };

package/dist/esm/node/vite/plugins/pluginViteConfigVikeExtensions.js

@@ -21,6 +21,8 @@ async function pluginViteConfigVikeExtensions() {
     }));
     const pluginsFromExtensions = (viteConfigFromExtensions.plugins ?? []);
     delete viteConfigFromExtensions.plugins;
+    // Avoid infinite loop
+    assertUsage(!pluginsFromExtensions.some((p) => p.name?.startsWith('vike:')), "Adding Vike's Vite plugin using +vite is forbidden");
     return [
         ...pluginsFromExtensions,
         {

package/dist/esm/node/vite/shared/resolveVikeConfigInternal/resolvePointerImport.js

@@ -73,8 +73,10 @@ function resolveImportPathWithNode(pointerImportData, importerFilePath, userRoot
     });
     if (!filePathAbsoluteFilesystem) {
         assert(!isImportPathRelative(pointerImportData.importPath));
+        /* This assertion fails if the npm package has a wrongly defined package.json#exports
         // Libraries don't use path aliases => filePathAbsoluteFilesystem should be defined
-        assert(!importerFilePathAbsolute.includes('node_modules'));
+        assert(!importerFilePathAbsolute.includes('node_modules'))
+        */
     }
     return filePathAbsoluteFilesystem;
 }

package/dist/esm/types/defineConfig.d.ts

@@ -1,3 +1,3 @@
 export { defineConfig };
 import type { Config } from './Config.js';
-declare function defineConfig(config: Config): Config;
+declare function defineConfig<T extends Config>(config: T): T;

package/dist/esm/types/defineConfig.js

@@ -1,4 +1,6 @@
 export { defineConfig };
+// For JavaScript users. AFAICT there isn't another practical reason to use defineConfig() instead of `Config`.
+// https://github.com/vikejs/vike/issues/1156
 function defineConfig(config) {
     return config;
 }

package/dist/esm/utils/PROJECT_VERSION.d.ts

@@ -1 +1 @@
-export declare const PROJECT_VERSION: "0.4.246";
+export declare const PROJECT_VERSION: "0.4.247";

package/dist/esm/utils/PROJECT_VERSION.js

@@ -1,2 +1,2 @@
 // Automatically updated by @brillout/release-me
-export const PROJECT_VERSION = '0.4.246';
+export const PROJECT_VERSION = '0.4.247';

package/dist/esm/utils/assert.js

@@ -41,7 +41,7 @@ function assert(condition, debugInfo) {
             return null;
         }
         const debugInfoSerialized = typeof debugInfo === 'string' ? debugInfo : JSON.stringify(debugInfo);
-        return pc.dim(`Debug info for Vike maintainers (you can ignore this): ${debugInfoSerialized}`);
+        return pc.dim(`Debug for maintainers (you can ignore this): ${debugInfoSerialized}`);
     })();
     const link = pc.underline('https://github.com/vikejs/vike/issues/new?template=bug.yml');
     let errMsg = [

package/dist/esm/utils/requireResolve.d.ts

@@ -5,7 +5,7 @@ export { requireResolveDistFile };
 export { getPackageNodeModulesDirectory };
 declare function requireResolveOptional({ importPath, importerFilePath, userRootDir, }: {
     importPath: string;
-    importerFilePath: string;
+    importerFilePath: string | null;
     userRootDir: string;
 }): string | null;
 declare function requireResolveOptionalDir({ importPath, importerDir, userRootDir, }: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vike",
-  "version": "0.4.246",
+  "version": "0.4.247",
   "repository": "https://github.com/vikejs/vike",
   "exports": {
     "./server": {
@@ -15,7 +15,8 @@
       "types": "./dist/esm/client/runtime-server-routing/index.d.ts"
     },
     "./types": {
-      "types": "./dist/esm/types/index.d.ts"
+      "types": "./dist/esm/types/index.d.ts",
+      "default": "./dist/esm/types/index.js"
     },
     "./client/router": {
       "worker": "./dist/esm/node/client/router.js",