fix: rename vike-pointer => vike:pointer

BREAKING CHANGE: `with { type: 'vike-pointer' }` renamed to `with { type: 'vike:pointer' }`

Author: brillout

docs/headings.ts

@@ -11,7 +11,7 @@ import {
   iconGlobe,
   iconPlug,
   iconMegaphone,
-} from '@brillout/docpress' with { type: 'vike-pointer' }
+} from '@brillout/docpress' with { type: 'vike:pointer' }
 import type {
   HeadingDefinition,
   Config,

docs/pages/config/+Page.mdx

@@ -396,7 +396,7 @@ You can manually mark an import to be a pointer import:
 // /pages/+config.ts
 // Environment: config
 
-import ssr from './ssr' with { type: 'vike-pointer' }
+import ssr from './ssr' with { type: 'vike:pointer' }
 console.log(ssr) // import:./ssr:default
 ```
 

docs/pages/error/runtime-in-config/+Page.mdx

@@ -41,7 +41,7 @@ Or this:
 // ✅ Allowed: same as defining +title.ts
 
 import type { Config } from 'vike/types'
-import title from './title' with { type: 'vike-pointer' }
+import title from './title' with { type: 'vike:pointer' }
 
 export default {
   title

packages/vike/src/node/vite/plugins/pluginStripPointerImportAttribute.ts

@@ -1,6 +1,6 @@
 export { pluginStripPointerImportAttribute }
 
-// Strip `with { type: 'vike-pointer' }` import attributes from files transpiled for the
+// Strip `with { type: 'vike:pointer' }` import attributes from files transpiled for the
 // client/server runtime. These attributes are only meaningful at config-time (they tell
 // Vike to treat the import as a pointer import); leaving them in runtime bundles would
 // break bundlers/runtimes that don't support unknown import attributes.
@@ -9,8 +9,8 @@ import type { Plugin } from 'vite'
 import { getMagicString } from '../shared/getMagicString.js'
 import '../assertEnvVite.js'
 
-// Match `with { type: 'vike-pointer' }` (with optional whitespace variations)
-const runtimeAttrRE = /\bwith\s*\{\s*type\s*:\s*['"]vike-pointer['"]\s*\}/g
+// Match `with { type: 'vike:pointer' }` (with optional whitespace variations)
+const runtimeAttrRE = /\bwith\s*\{\s*type\s*:\s*['"]vike:pointer['"]\s*\}/g
 
 function pluginStripPointerImportAttribute(): Plugin[] {
   return [
@@ -19,7 +19,7 @@ function pluginStripPointerImportAttribute(): Plugin[] {
       transform: {
         filter: {
           code: {
-            include: 'vike-pointer',
+            include: 'vike:pointer',
           },
         },
         handler(code, id) {

packages/vike/src/node/vite/shared/resolveVikeConfigInternal/transpileAndExecuteFile.ts

@@ -251,7 +251,7 @@ async function transpileWithEsbuild(
             //      - 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 ||
-            args.with?.['type'] === 'vike-pointer'
+            args.with?.['type'] === 'vike:pointer'
 
           assertPosixPath(importPathResolved)
           // False positive if `importPathOriginal` is a path alias that a) looks like an npm package import and b) resolves outside of `userRootDir` => we then we wrongfully assume that `importPathOriginal` is an npm package import.