vike 0.4.253-commit-468c8a0 → 0.4.253-commit-aa63f56

package/dist/node/vite/shared/resolveVikeConfigInternal/transpileAndExecuteFile.js

@@ -182,11 +182,9 @@ async function transpileWithEsbuild(filePath, userRootDir, transformImports, esb
                     //   - assertIsImportPathNpmPackage()
                     //   - isImportPathNpmPackage(str, { cannotBePathAlias: true })
                     assertFilePathAbsoluteFilesystem(importPathResolved);
-                    // Non-script file (e.g. .svg, .css) or explicitly tagged as runtime-only
-                    // (`import url from './logo.svg' with { type: 'runtime' }`) => resolve to
-                    // constant string so that files with `env: { config: true, client: true }`
-                    // can also be loaded in Node.js
-                    if (!isScriptFile(importPathResolved) || args.with?.['type'] === 'runtime') {
+                    // Non-script file (e.g. .svg, .css) => resolve to constant string so that files with
+                    // `env: { config: true, client: true }` can also be loaded in Node.js
+                    if (!isScriptFile(importPathResolved)) {
                         esbuildCache.vikeConfigDependencies.add(importPathResolved);
                         return {
                             path: importPathResolved,
@@ -203,7 +201,9 @@ async function transpileWithEsbuild(filePath, userRootDir, transformImports, esb
                         //    - In principle, we can use the setting 'name' value of Vike extensions.
                         //      - vike@0.4.162 started soft-requiring Vike extensions to set the name config.
                         //    - In practice, it seems like it requires some (non-trivial?) refactoring.
-                        isVikeExtensionImport;
+                        isVikeExtensionImport ||
+                        // Explicitly tagged as runtime code => pointer import
+                        args.with?.['type'] === 'runtime';
                     assertPosixPath(importPathResolved);
                     // `isNpmPkgImport` => `importPathOriginal` is most likely an npm package import, but it can also be a path alias that a) looks like an npm package import and b) resolves outside of `userRootDir`.
                     const isNpmPkgImport = (() => {

package/dist/utils/PROJECT_VERSION.d.ts

@@ -1 +1 @@
-export declare const PROJECT_VERSION: "0.4.253-commit-468c8a0";
+export declare const PROJECT_VERSION: "0.4.253-commit-aa63f56";

package/dist/utils/PROJECT_VERSION.js

@@ -1,2 +1,2 @@
 // Automatically updated by @brillout/release-me
-export const PROJECT_VERSION = '0.4.253-commit-468c8a0';
+export const PROJECT_VERSION = '0.4.253-commit-aa63f56';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vike",
-  "version": "0.4.253-commit-468c8a0",
+  "version": "0.4.253-commit-aa63f56",
   "repository": "https://github.com/vikejs/vike",
   "exports": {
     "./server": {