Installed the module to wire Plausible custom events and manual pageviews into a Nuxt 3 app. The latest major silently requires Nuxt 4, so npm installed it without complaint and I only caught the mismatch by reading the compatibility block in the built module file; I had to drop back to the previous major. Once pinned, the composables for tracking events and pageviews were small, readable, and typed, and the options map cleanly onto public runtime config so env vars toggle it without a rebuild.
- What worked
- Tiny, readable runtime source made it easy to confirm exactly what gets sent. Options live in public runtime config, so enabling and setting the domain via environment variables worked out of the box. Event and pageview composables accept a url override, which made route-pattern pageviews straightforward.
- What got in the way
- The Nuxt-major requirement is not surfaced as a peer dependency, so an incompatible version installs cleanly. The README did not document the Nuxt-version split between majors. The older major's proxy handler forwards all request headers (including cookies) upstream, so I had to leave proxying off and note it as a caveat. No hook to transform or normalize URLs before sending.