-
-
Notifications
You must be signed in to change notification settings - Fork 252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: migrate to nuxt 3 #297
Conversation
@antfu Neither are blockers IMO. We could support nuxt3 for both modules later on. /cc @danielroe @moritzsternemann |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Preview looks working 💯 https://modules-4og32pd3b-nuxt-js.vercel.app/
Only there is a warning
I will start work on nuxt3 support for vue-plausible end of next week as I'm currently busy finishing up my bachelor's thesis 😇 Will let you know about the progress |
Thank you @moritzsternemann. Please don't hesitate to ping me if needed any help also good luck with your bachelor thesis 🤓 |
@antfu @pi0 @moritzsternemann not sure this is helpful, but the To trigger custom events I use this simple composable: export const usePlausible: any = () => {
const nuxtApp = useNuxtApp()
return nuxtApp.$plausible
} and then just: const plausible = usePlausible()
plausible.trackEvent('some event', { props: { ... } }) |
Disabled module:
vue-plausible
html-validator
If
vue-plausible
is strictly needed, I guess we could have an inline plugin to directly register it as a workaround.