bridge: _nuxt/empty.js was blocked with vite:true and ssr:false

Environment


  • Operating System: Linux
  • Node Version: v14.19.3
  • Nuxt Version: 2.16.0-27720022.54e852f
  • Nitro Version: 0.5.4
  • Package Manager: yarn@1.22.19
  • Builder: vite
  • User Config: bridge, ssr, serverHandlers, devServerHandlers, buildModules
  • Runtime Modules: -
  • Build Modules: (), @nuxt/bridge@3.0.0-27740081.058a6c1

Reproduction

  1. Open the default CodeSandbox template: https://codesandbox.io/p/github/nuxt/starter/tree/v2-bridge-codesandbox
  2. Replace nuxt.config.js with this:
import { defineNuxtConfig } from "@nuxt/bridge";

export default defineNuxtConfig({
  bridge: {
    vite: true
  },

  ssr: false
});

(or open this CodeSandbox where I already replaced the config: https://codesandbox.io/s/nuxt-bridge-vite-empty-error-ee3gjg?file=/nuxt.config.js)

  1. In Firefox, open the console (the error does not show in the sandbox console) and see the error:
Loading module from “https://ee3gjg.sse.codesandbox.io/_nuxt/empty.js” was blocked because of a disallowed MIME type (“text/html”).
Loading failed for the module with source “https://ee3gjg.sse.codesandbox.io/_nuxt/empty.js”.
  1. In Chrome open the console and see the error:
empty.js: Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/html". Strict MIME type checking is enforced for module scripts per HTML spec.
  1. See that the page does not load

Describe the bug

When using vite: true and ssr: false in Nuxt/bridge, the page does not load and in your browser console you find an error telling that the file empty.js was blocked because it has the wrong MIME-type.

Additional context

No response

Logs

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 22
  • Comments: 20 (4 by maintainers)

Most upvoted comments

👍 , facing the same issue

Does anybody know a workaround for this issue? Our “nuxi dev” gets slower and slower, so we would really like to use Vite soon.

We are facing the same issue too.

thanks @AndreyYolkin I’m one step closer. Now experiencing the same ENOENT issue.

Same here, setting ssr:false gives this error.