🚸 Use dynamic import for WASI in loadPrism

- To delay the warning `ExperimentalWarning: WASI is an experimental feature and might change at any time` for prism/wasm until the actual moment prism is used.
- Introduced the `renameImportWasi` plugin to address an issue where `import 'wasi';` was being included in the build artifact despite being dynamically imported within the `db-structure` package.

.changeset/blue-worms-retire.md

@@ -0,0 +1,6 @@
+---
+"@liam-hq/db-structure": patch
+"@liam-hq/cli": patch
+---
+
+:children_crossing: Delay the warning `ExperimentalWarning: WASI is an experimental feature and might change at any time` for prism/wasm until the actual moment prism is used.

frontend/packages/cli/vite-plugins/index.ts

@@ -1 +1,2 @@
+export * from './remove-import-wasi.js'
 export * from './set-env.js'

frontend/packages/cli/vite-plugins/remove-import-wasi.ts

@@ -0,0 +1,19 @@
+import fs from 'fs'
+import { type Plugin } from 'vite'
+
+// The `import 'wasi'` statement is dynamically imported within the db-structure package.
+// However, `import 'wasi';` gets included in the build output.
+// To address this, the buildEnd hook removes it from the build artifact.
+export function renameImportWasi(): Plugin {
+  return {
+    name: 'remove-import-wasi',
+    buildEnd() {
+      const filePath = 'dist-cli/bin/cli.js'
+      const originalContent = fs.readFileSync(filePath, 'utf8')
+      const content = originalContent.replace(/import 'wasi';\s*/g, '')
+      fs.writeFileSync(filePath, content, 'utf8')
+    },
+  }
+}
+
+export default renameImportWasi

frontend/packages/cli/vite.config.ts

@@ -2,7 +2,7 @@ import { rmSync } from 'node:fs'
 import react from '@vitejs/plugin-react'
 import tsconfigPaths from 'vite-tsconfig-paths'
 import { defineConfig } from 'vitest/config'
-import { setEnvPlugin } from './vite-plugins/index.js'
+import { renameImportWasi, setEnvPlugin } from './vite-plugins/index.js'
 
 const outDir = 'dist-cli/html'
 
@@ -26,7 +26,12 @@ export default defineConfig({
       ],
     },
   },
-  plugins: [react(), tsconfigPaths(), setEnvPlugin()],
+  plugins: [
+    react(),
+    tsconfigPaths(),
+    renameImportWasi(),
+    setEnvPlugin(),
+  ],
   test: {
     globals: true,
     environment: 'node',

frontend/packages/db-structure/src/parser/schemarb/loadPrism.ts

@@ -16,8 +16,7 @@ Consider removing this patch once support for Node.js v18 is no longer necessary
 import { readFile } from 'node:fs/promises'
 // biome-ignore lint/correctness/noNodejsModules: This import is server-side specific because loadPrism() is exclusively invoked in server environments.
 import { fileURLToPath } from 'node:url'
-// biome-ignore lint/correctness/noNodejsModules: This import is server-side specific because loadPrism() is exclusively invoked in server environments.
-import { WASI } from 'node:wasi'
+
 import type { ParseResult } from '@ruby/prism/src/deserialize.js'
 import { parsePrism } from '@ruby/prism/src/parsePrism.js'
 
@@ -32,6 +31,9 @@ export async function loadPrism(): Promise<(source: string) => ParseResult> {
     overrideWasmUrl ?? fileURLToPath(new URL('prism.wasm', import.meta.url))
   const wasm = await WebAssembly.compile(await readFile(path))
 
+  // Dynamic import for WASI to avoid warnings unless necessary
+  // biome-ignore lint/correctness/noNodejsModules: This import is server-side specific because loadPrism() is exclusively invoked in server environments.
+  const { WASI } = await import('node:wasi')
   const wasi = new WASI({ version: 'preview1' })
 
   // Patch applied for compatibility