vike 0.4.176-commit-1442a4a → 0.4.177

package/dist/cjs/node/runtime/renderPage/handleErrorWithoutErrorPage.js

@@ -35,8 +35,8 @@ function warnMissingErrorPage(isV1) {
     if (!globalContext.isProduction) {
         const msg = [
             `No ${isV1 ? 'error page' : picocolors_1.default.cyan('_error.page.js')} found,`,
-            'we recommend defining an error page,',
-            'see https://vike.dev/error-page'
+            'we recommend defining one',
+            'https://vike.dev/error-page'
         ].join(' ');
         (0, utils_js_1.assertWarning)(false, msg, { onlyOnce: true });
     }

package/dist/cjs/utils/assertSingleInstance.js

@@ -1,4 +1,7 @@
 "use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.onAssertModuleLoad = exports.onClientEntry_ClientRouting = exports.onClientEntry_ServerRouting = void 0;
 //  - Throw error if there are two different versions of vike loaded
@@ -7,6 +10,7 @@ exports.onAssertModuleLoad = exports.onClientEntry_ClientRouting = exports.onCli
 const unique_js_1 = require("./unique.js");
 const getGlobalObject_js_1 = require("./getGlobalObject.js");
 const projectInfo_js_1 = require("./projectInfo.js");
+const picocolors_1 = __importDefault(require("@brillout/picocolors"));
 /* Use original assertUsage() & assertWarning() after all CJS is removed from node_modules/vike/dist/
 import { assertUsage, assertWarning } from './assert.js'
 */
@@ -21,7 +25,7 @@ function assertSingleInstance() {
         const versions = (0, unique_js_1.unique)(globalObject.instances);
         assertUsage(versions.length <= 1, 
         // DO *NOT* patch vike to remove this error: because of multiple conflicting versions, you *will* eventually encounter insidious issues that hard to debug and potentially a security hazard, see for example https://github.com/vikejs/vike/issues/1108
-        `Both vike@${versions[0]} and vike@${versions[1]} loaded. Only one version should be loaded.`);
+        `vike@${picocolors_1.default.bold(versions[0])} and vike@${picocolors_1.default.bold(versions[1])} loaded but only one version should be loaded`);
     }
     if (globalObject.checkSingleInstance && globalObject.instances.length > 1) {
         /*/ Not sure whether circular dependency can cause problems? In principle not since client-side code is ESM.

package/dist/cjs/utils/projectInfo.js

@@ -1,7 +1,7 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.PROJECT_VERSION = exports.projectInfo = void 0;
-const PROJECT_VERSION = '0.4.176-commit-1442a4a';
+const PROJECT_VERSION = '0.4.177';
 exports.PROJECT_VERSION = PROJECT_VERSION;
 const projectInfo = {
     projectName: 'Vike',

package/dist/esm/node/runtime/renderPage/handleErrorWithoutErrorPage.js

@@ -29,8 +29,8 @@ function warnMissingErrorPage(isV1) {
     if (!globalContext.isProduction) {
         const msg = [
             `No ${isV1 ? 'error page' : pc.cyan('_error.page.js')} found,`,
-            'we recommend defining an error page,',
-            'see https://vike.dev/error-page'
+            'we recommend defining one',
+            'https://vike.dev/error-page'
         ].join(' ');
         assertWarning(false, msg, { onlyOnce: true });
     }

package/dist/esm/shared/page-configs/PageConfig.d.ts

@@ -67,9 +67,9 @@ type ConfigEnv = {
 /** For Vike internal use */
 type ConfigEnvInternal = Omit<ConfigEnv, 'client'> & {
     client?: boolean | 'if-client-routing';
-    /** Always load value, not matter what page is loaded. */
-    eager?: boolean;
-    /** Load value only in production or only in development. */
+    /** Always load value, no matter which page is loaded. */
+    eager?: true;
+    /** Load value only in production, or only in development. */
     production?: boolean;
 };
 type ConfigValueSource = {

package/dist/esm/utils/assertSingleInstance.js

@@ -7,6 +7,7 @@ export { onAssertModuleLoad };
 import { unique } from './unique.js';
 import { getGlobalObject } from './getGlobalObject.js';
 import { projectInfo } from './projectInfo.js';
+import pc from '@brillout/picocolors';
 /* Use original assertUsage() & assertWarning() after all CJS is removed from node_modules/vike/dist/
 import { assertUsage, assertWarning } from './assert.js'
 */
@@ -21,7 +22,7 @@ function assertSingleInstance() {
         const versions = unique(globalObject.instances);
         assertUsage(versions.length <= 1, 
         // DO *NOT* patch vike to remove this error: because of multiple conflicting versions, you *will* eventually encounter insidious issues that hard to debug and potentially a security hazard, see for example https://github.com/vikejs/vike/issues/1108
-        `Both vike@${versions[0]} and vike@${versions[1]} loaded. Only one version should be loaded.`);
+        `vike@${pc.bold(versions[0])} and vike@${pc.bold(versions[1])} loaded but only one version should be loaded`);
     }
     if (globalObject.checkSingleInstance && globalObject.instances.length > 1) {
         /*/ Not sure whether circular dependency can cause problems? In principle not since client-side code is ESM.

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

@@ -1,7 +1,7 @@
 export { projectInfo };
 export { PROJECT_VERSION };
-declare const PROJECT_VERSION: "0.4.176-commit-1442a4a";
+declare const PROJECT_VERSION: "0.4.177";
 declare const projectInfo: {
     projectName: "Vike";
-    projectVersion: "0.4.176-commit-1442a4a";
+    projectVersion: "0.4.177";
 };

package/dist/esm/utils/projectInfo.js

@@ -1,6 +1,6 @@
 export { projectInfo };
 export { PROJECT_VERSION };
-const PROJECT_VERSION = '0.4.176-commit-1442a4a';
+const PROJECT_VERSION = '0.4.177';
 const projectInfo = {
     projectName: 'Vike',
     projectVersion: PROJECT_VERSION

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vike",
-  "version": "0.4.176-commit-1442a4a",
+  "version": "0.4.177",
   "scripts": {
     "dev": "tsc --watch",
     "build": "rimraf dist/ && pnpm run build:esm && pnpm run build:cjs",