🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ 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

This adds support for detecting a /module subpath and loading it where it exists.

This would mean a project that is primarily a library can ship a Nuxt module as /module and support adding just the root library name to modules: [].

Example

  export default defineNuxtConfig({
    modules: [
-    'some-library/module'
+    'some-library'
    ]
  })

(We can, for example, use this straight away for @nuxt/test-utils/module.)

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.