fix: handle optional chaining for imports in setupImportMocking function

[ExEr7um]

🔗 Linked issue

None.

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Problem

The setupImportMocking function was failing when presets contained string values (e.g., vitest) instead of objects with an imports property.

export default defineNuxtConfig({
  imports: { presets: ["vitest"] },
})

This caused a TypeError when trying to access p.imports on string presets, breaking test execution.

⎯⎯⎯⎯ Startup Error ⎯⎯⎯⎯
TypeError: Cannot read properties of undefined (reading 'includes')

Solution

Added optional chaining (?.) to safely check if the imports property exists before calling .includes('setInterval'). This prevents errors when presets are strings rather than objects with an imports array.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@nuxt/test-utils@1433

commit: 2b351f1