Matteo Gabriele comments

Results 50 comments of


                                            Matteo Gabriele

customResourceURL, with MV3 extension

I'm not sure what this is about

Rollup failed to resolve import "vue-gtag" from "/workspace/src/main.ts"

I'm not sure how to help you with this one. Did you manage to fix it?

Problem with nuxt imports: Vitest Coverage stays at 100% for components regardless of the existence of any component test because of nuxt imports

I'm experiencing a similar issue. I created a small application to identify which package was causing the problem, and it appears to be Vitest v3 when testing a Nuxt 3...

Problem with nuxt imports: Vitest Coverage stays at 100% for components regardless of the existence of any component test because of nuxt imports

The test repository contains a component and a page with the same code and tests. The main branch uses Vitest 3 but with the broken code coverage. There is another...

Problem with nuxt imports: Vitest Coverage stays at 100% for components regardless of the existence of any component test because of nuxt imports

just wanted to point out that similar issues with code coverage and Vitest v3 have been spotted in the i18n module https://github.com/nuxt-modules/i18n/issues/3238#issuecomment-2672492536 Maybe it helps, maybe it doesn't. In my...

Problem with nuxt imports: Vitest Coverage stays at 100% for components regardless of the existence of any component test because of nuxt imports

To eliminate any uncertainties, I have made the exact same application using plain Vue, VueRouter, and Vitest, and it works as expected without any issues. I had to try it.

Problem with nuxt imports: Vitest Coverage stays at 100% for components regardless of the existence of any component test because of nuxt imports

The coverage will work if I change the folder name of "pages" to "views", for example. It's important to note that changing the value of `dir.pages` in the nuxt.config file...

Problem with nuxt imports: Vitest Coverage stays at 100% for components regardless of the existence of any component test because of nuxt imports

@jsedanoj not really. I thought that this was a nuxt error since it is so specific about pages.

Problem with nuxt imports: Vitest Coverage stays at 100% for components regardless of the existence of any component test because of nuxt imports

I completely get the frustration, but just a reminder that open source relies on community effort. It’s important to stay constructive and supportive so we can all work together to...

Problem with nuxt imports: Vitest Coverage stays at 100% for components regardless of the existence of any component test because of nuxt imports

@jsedanoj, no worries! If you are using Nuxt 2, you must have had a moment before the recent updates when you were able to achieve the correct coverage, right? Have...