@symbiote-native/vue 0.3.3 → 0.3.5

package/metro-vue-transformer.cjs

@@ -13,8 +13,18 @@
 // Ships as a package-level export (`@symbiote-native/vue/metro-vue-transformer`) rather than living
 // in each consuming app: a consumer's own metro.config.js just points babelTransformerPath at it.
 
-const { parse, compileScript } = require('@vue/compiler-sfc');
+const nodeFs = require('fs');
+const { parse, compileScript, registerTS } = require('@vue/compiler-sfc');
 const { createCompoundExpression } = require('@vue/compiler-core');
+
+// A bare-specifier type import (`import type { X } from '@symbiote-native/navigation/vue'`, as
+// opposed to a relative one) needs real node_modules resolution (package.json exports, pnpm
+// symlinks) to turn the specifier into a file path — compileScript's own `fs` option only reads
+// paths it's already given, it can't do that resolution. @vue/compiler-sfc's sanctioned hook for
+// this is `registerTS`, the same one @vitejs/plugin-vue and vue-tsc call: it hands the compiler a
+// lazy loader for the real `typescript` package, which resolves the specifier via
+// `ts.resolveModuleName` and self-supplies `ts.sys` as the fs fallback.
+registerTS(() => require('typescript'));
 // @symbiote-native/css-parser is a real dependency of THIS package, so requiring it directly here
 // (rather than through the ./metro-css-parser public subpath, which exists for CONSUMERS) resolves
 // straight from this package's own node_modules under pnpm.
@@ -31,6 +41,23 @@ const {
 
 const upstreamTransformer = resolveUpstreamTransformer();
 
+// compileScript needs file system access to resolve a type-only `defineProps<ISomeProps>()`
+// where ISomeProps is imported from another file — without it, Metro's worker process (a real
+// Node process, but one @vue/compiler-sfc doesn't auto-detect as Node unless the consumer calls
+// its `registerTS` hook) throws "No fs option provided ... in non-Node environment". Wiring
+// Node's own `fs` module straight through is simpler than registering the `typescript` package
+// as a loader (registerTS), and this file already runs in Node at Metro build time.
+const compileScriptFs = {
+  fileExists: (file) => nodeFs.existsSync(file),
+  readFile: (file) => {
+    try {
+      return nodeFs.readFileSync(file, 'utf-8');
+    } catch {
+      return undefined;
+    }
+  },
+};
+
 // Rewrites a Vue template AST so every `class`/`:class` binding on an element resolves
 // against this file's scoped class names at the compiled call site, via @symbiote-native/engine's
 // scopeClassName(value, localNames, scopeId). This runs at the AST level rather than as a
@@ -234,6 +261,7 @@ async function compileSfc(src, filename) {
     id: scopeId,
     inlineTemplate: true,
     templateOptions,
+    fs: compileScriptFs,
   });
   // Point every Vue import (the compiler's injected helpers AND the user's own
   // `import { ref } from 'vue'`) at the runtime-helpers shim, which re-exports the same

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@symbiote-native/vue",
-  "version": "0.3.3",
+  "version": "0.3.5",
   "description": "SymbioteNative's Vue adapter — a @vue/runtime-core createRenderer driving real native iOS/Android views through the same engine as the React adapter.",
   "repository": {
     "type": "git",
@@ -44,9 +44,10 @@
     "@vue/compiler-core": "^3.5.13",
     "@vue/compiler-sfc": "^3.5.13",
     "@vue/runtime-core": "^3.5.13",
-    "@symbiote-native/components": "0.2.3",
+    "typescript": "~6.0.0",
+    "@symbiote-native/components": "0.2.4",
     "@symbiote-native/css-parser": "0.2.1",
-    "@symbiote-native/engine": "0.1.4"
+    "@symbiote-native/engine": "0.1.5"
   },
   "peerDependencies": {
     "vue": ">=3.5.0",