feat(nuxt3): rewrite with nuxt kit

[Baroshem]

In this PR I wanted to introduce some Breaking Changes for the configuration of the module for both Google Analytics and Vercel Analytics.

I wanted to add both these variables as a part of the module config options like this:

interface ModuleOptions {
  provider: 'log' | 'vercel' | 'ga';
  debug: boolean;
  disabled: boolean;
  options: {
    googleMeasurementId: '123test',  // <- for Google Analytics
    vercelAnalyticsDsn: '123test'  // <- for Vercel Analytics
  }
}

Apart from that, no other BC are introduced in the migration and the module should work for all nuxt.js projects due to usage of module-builder.

[atinux]

Would love to know @pi0 thoughts on my comments

[Baroshem]

@pi0 @atinux @danielroe I have added all recommendations from you :)

[pi0]

What it is used for?

[Baroshem]

It was there before, I can remove it :)

[pi0]

We are already setting default to log in L44 :)

[pi0]

Why you removed log utils? :)

[Baroshem]

It was used in one place and basically had the same purpose as regular console.log.

[Baroshem]

@pi0 @atinux @danielroe

I have updated the PR with the recent recommendations.

[atinux]

Would be nice to have an edge release in order to try it out :)

[Baroshem]

@atinux Could you explain what do you mean about edge release?

I just created a PR with a update to Nuxt 3 so i dont have access to deploy the package. I believe it would be up to @pi0 to do that

[atinux]

I was thinking that you could try to release on a nuxt-webvitals-module to try it for example.

Do you mind resolving the conflicts @Baroshem ?

[pi0]

Current module should be compatible with Nuxt 3. I'm holding on this PR to properly test for Nuxt 3 and Nuxt 2 compatibility (vercel auto installs this module on deployments) and also check provider resolution changes.

[atinux]

This is why I was thinking of an edge deployment to test on Vercel for example on one of our Nuxt 3 projects, how to test it otherwise?

[AndrewBogdanovTSS]

Hi guys, any updates on this one?

[atinux]

So far the module is working also on Nuxt 3.

I would personally vote to have a branch for Nuxt 2 and another one for Nuxt 3 for simplicity.

[pi0]

@Baroshem I reworked migration to kit with 3.0.0 compatibility in #59 to be without breaking changes and remain nuxt 2 compatible (mainly because vercel is injecting this module automatically).

Your PR included some more changes and type improvements that were conflicting. Feel free to rework them as smaller PRs and thanks again for time spent on this migration ❤️