Closed junemolison closed 4 months ago
Name | Link |
---|---|
Latest commit | fb6106dbd4bc08b2deb46bbedcc0e5da2a1d1de3 |
Latest deploy log | https://app.netlify.com/sites/nuxt-gtag/deploys/668bc74bd5bf720007f39e88 |
Deploy Preview | https://deploy-preview-82--nuxt-gtag.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Thanks for the PR! But why not keep #imports
, do you run into any issues?
I believe using #imports
is the correct way here, as all other Nuxt modules use it at the moment. For example:
chore: release v2.0.7 chore: update deps fix: ensure plugin types are exposed
🔗 Linked issue
📚 Description
Fixed import of defineNuxtPlugin to properly expose types accordingly to template: https://github.com/nuxt/starter/blob/module/src/runtime/plugin.ts