升级npm后出现无法在客户端代码访问util.inspect的Sass错误求助

Based on your error details and the underlying Vite compatibility context, here are actionable solutions to resolve this util.inspect browser runtime error:

1. Clean up conflicting Sass dependencies #

You’re using both node-sass and sass (dart-sass) simultaneously, which creates unexpected runtime conflicts—especially since node-sass is no longer maintained. Let’s simplify your dependency stack:

• Uninstall node-sass entirely:

  npm uninstall node-sass
  

• Upgrade sass-loader to a version optimized for Nuxt 3 and Vite. The latest stable 13.x+ versions resolve many integration bugs:

  npm install sass-loader@latest --save-dev
  

2. Tweak Vite config to handle util correctly #

Vite’s default behavior externalizes Node.js built-in modules like util for browser environments, but Sass’s dart runtime tries to access util.inspect which doesn’t exist client-side. Fix this by updating your nuxt.config.ts:

export default defineNuxtConfig({
  vite: {
    // Stop Vite from externalizing `util` for browser/SSR contexts
    ssr: {
      noExternal: ['util']
    },
    // Alias `util` to a browser-compatible implementation
    resolve: {
      alias: {
        util: 'util/util.js'
      }
    },
    // Force pre-optimization of Sass dependencies to avoid runtime mismatches
    optimizeDeps: {
      include: ['sass']
    }
  }
})

3. Ensure server-side Sass logic doesn’t run client-side #

Double-check your components and plugins—make sure you aren’t calling Node.js-specific Sass compilation APIs (like custom variable parsers or build-time utilities) in client-side code. Move any such logic to Nuxt’s server directory or a server-only plugin to avoid executing it in the browser.

4. Upgrade Nuxt to a stable release #

Your current Nuxt version (3.0.0-rc.10) is an old release candidate with known Vite integration bugs. Upgrading to the latest stable Nuxt 3 version will resolve many of these edge cases out of the box:

npm install nuxt@latest --save-dev

Why this works #

The error stems from Vite blocking access to Node.js built-ins like util in browser code, while Sass’s dart runtime accidentally attempts to use util.inspect client-side. The steps above either eliminate conflicting dependencies, adjust Vite’s module handling rules, or upgrade to a framework version with fixed compatibility logic.

内容的提问来源于stack exchange，提问作者Jan Veselý