Nuxt Enterprise Plugin Patterns
summary
Nuxt deployments at RealTruck run for four years across 8 e‑commerce sites and endure about ~20 integrations, so the claim is that concentrated plugin files per provider keep pages clean, plugins run once per hit on server and again in the browser, and abstractions let code call chat.open regardless of vendor. Implementation details include lazy loading scripts, swapping providers without changing components, and using a mitt event bus to publish marketing events while warning against using it for component logic.
AI-written summary · about
chapters (6)
- 0:00Enterprise plugin patterns
- 1:15Third-party code problems
- 3:39Fixing third-party code with plugins
- 6:09Abstractions for service providers
- 10:24Marketing tracking with event bus
- 14:17Summary
related talks
23mNuxt: Making an Extensible Meta Framework
39mUnJS: Nuxt 3 behind the scenes
33mNew Developer Experiences with Nuxt 3
26mOptimising Developer Experience with Nuxt 3
24mDeveloper Experience with Nuxt
27mDX is the new black. Learnings from using Nuxt and Storybook at scale
25mHow Vite Makes Nuxt Possible
31mAn introduction to Nuxt Scripts