Nuxt module import in E2E environment

[peterbud]

Environment

---

• Operating System: Linux
• Node Version: v18.18.0
• Nuxt Version: 3.9.0
• CLI Version: 3.10.0
• Nitro Version: 2.8.1
• Package Manager: [email protected]
• Builder: -
• User Config: modules, devtools, runtimeConfig
• Runtime Modules: @nuxt/test-utils/[email protected], ()
• Build Modules: -

---

Reproduction

With the latest nuxt test-utils I was trying to mock a server side import. Before even able to mock the server side import, I have realized that the plain vanilla minimal nuxt module seems to be ignored/not executed when running e2e test.

See repro here:
https://stackblitz.com/edit/nuxt-vitest-x6ycht

Describe the bug

Basic setup is to have a server side import coming from a module. an API is using that import to return a value. Running pnpm dev works, and the API returns the value as expected.

Running an E2E test in the nuxt environment however fails, showing error messages which are hinting that the module import has not been executed:

(node-resolve plugin) Could not resolve import "#auth" in /home/projects/nuxt-vitest-x6ycht/server/api/test.get.ts using imports defined in /home/projects/nuxt-vitest-x6ycht/package.json.

Maybe my test config needs to be improved? Or is it a bug?

Additional context

No response

Logs

No response

[danielroe]

Currently the vitest environment only allows for testing client-side code. (So any aliases added to your nitro config are not respected.)

We can track supporting server side unit testing in #531.

[peterbud]

Thanks Daniel. I had the impression that E2E is also including the Nuxt server component. Thanks for the clarification.

[danielroe]

You can definitely test the server side with e2e, but that starts a server with setup and performs fetch requests to it. You don't directly import the server code into your test.