enabling @nuxt/components makes source-mapped files disappear from browser debugger

[violoncelloCH]

Describe the bug
I've run into this as newly, by npx create-nuxt-app created projects have set components: true by default. Wondering why I can't see the correctly source-mapped files in my browser console when trying to debug something, I finally found out that setting components: true in nuxt.config.js triggers this behaviour.

With nuxt/components disabled I can see the following in Firefox:

or in Chromium:

those *.vue files contain the correctly source-mapped code of my components. When setting components: true, those disappear and I'm unable to debug my code in the browser console.

To Reproduce

1. create a new nuxt app with npx create-nuxt-app (universal, static)
2. run nuxt or npm run dev to start the dev environment
3. see that the source-mapped component files under webpack are missing
4. remove components: true or set it to false (in nuxt.config.js)
5. see that the source-mapped component files are now there

Expected behavior
debugging with source-mapped vue-component files should be available regardless of components: true

Screenshots
see above

Additional context
I don't know who is maintaining the default for npx create-nuxt-app, but if this is a technical limitation of nuxt/components, maybe this shouldn't be enabled by default then...

[nicholasoxford]

Is there a follow up to this? This is causing issues for us.

[violoncelloCH]

no idea... I simply deactivated the component autoloading (components: true in nuxt.config.js) for now and import used components as I do in other vue applications...

[nicholasoxford]

I thought I would get smart and give it an alias, but with no success (it seems).

Its looking like I might have to undo the changes I did on my teams projects. I would really like an answer or a solution so I can keep this awesome feature. It made our pages much less verbose