Sébastien Chopin

Not really sure about this since App is always applied for Nuxt 3. We could patch Nuxt 2 `App.js` to use something like `this.app` instead of `'div'` here: https://github.com/nuxt/nuxt.js/blob/dev/packages/vue-app/template/App.js#L46 But...

I think the usage will be different, I think that for Nuxt Bridge user they will have to use `` in order to display the layout/page (https://github.com/nuxt/nuxt.js/blob/dev/packages/vue-app/template/App.js#L73-L81). Where in Nuxt...

I think that this is definitely something we should try anyway since it will ease the migration. I just want to be more confident about the usage of NuxtPage with...

Happy to add it once Nuxt 3 support lands, tracking on https://github.com/dword-design/nuxt-mail/issues/108

Last updated as last released at?

I guess we can use the `pushed_at` attribute from GH API: https://api.github.com/repos/nuxt/image Would be nice to have the last release date from NPM, but I struggled to find the API...

> GET on http://registry.npmjs.org/nuxt-image and we get extract the time.modified which seems to be the last published version Perfect then!

Agree with @pi0 I see two things: - Using @nuxt/modules as a package, it should not include stars, download and last release - Using it as API for the website...

I would personnaly rename it to `h3-validator` (but fine with `h3-typebox` if listed in Readme as validator options) and support the new `event` object @kevinmarrec 😊 Awesome work so far...

Regarding #9 I don't see a use case so far. For the convention to override, I believe `NUXT_EXTENDS` is a special case since it is a special feature: https://github.com/unjs/c12#extending-configuration