Puter

This error occurs in puter.com v2.5.1 on Windows because the extension loader uses an absolute Windows path (e.g., 'c:\\...') without the required file:// prefix, which Node.js ESM loader rejects. Workaround: Run Node.js with the --experimental-specifier-resolution=node flag. Modify the start script in package.json or run directly: node --enable-source-maps --experimental-specifier-resolution=node -r ./dist/src/backend/telemetry.js ./dist/src/backend/index.js. Alternatively, patch the extension loading code to convert absolute paths to file:// URLs. Long-term fix: update to a newer puter.com version that handles Windows paths correctly.

The error occurs because the Node-compatible bundle of @heyputer/puter.js (which uses socket.io‑client's .unref()) is loaded on the client side. Force Nuxt to use the browser build with a client‑only plugin:

1. Create plugins/puter.client.ts:

export default defineNuxtPlugin(async (nuxtApp) => {
  const mod = await import('@heyputer/puter.js/dist/puter.js'); // browser bundle
  const puter = mod.puter ?? mod.default ?? mod;
  nuxtApp.provide('puter', puter);
});

export default defineNuxtConfig({
  ssr: false, // ensure client‑side only
  vite: {
    optimizeDeps: {
      exclude: ['@heyputer/puter.js']
    }
  }
});