This section documents version-specific API changes for @nuxt/hints v1.1.3.
-
Use partial feature configuration to selectively debug specific areas — configure only the feature you're fixing and disable others to reduce console noise source
-
Configure features as objects with { logs, devtools, options } flags rather than just booleans for granular control over whether warnings appear in console vs DevTools only source
-
Expect hydration detection to produce false positives when components mount — the module relies on Vue's onMounted hook rather than a dedicated hydration mismatch hook, so timing differences can trigger spurious warnings source
-
Keep the DevTools panel connected during development when using lazy-load detection — if the client disconnects, lazy-load reporting via birpc times out and crashes the dev server (fixed in v1.1.2 but still worth avoiding) source
-
Disable htmlValidate or carefully manage SVG structures in your markup — the feature uses Prettier's HTML parser which cannot handle SVG-to-HTML namespace transitions (e.g., SVG with nested <picture> elements inside <foreignObject>) source
-
Apply the Windows path alias workaround if #hints-config fails to resolve on Windows — use a manual alias in nuxt.config.ts to point to a local hints.config.ts file source
-
Use Lazy prefix (e.g., <LazyHeavyComponent>) or defineAsyncComponent for component suggestions — lazy-load detection identifies statically imported components but relies on your components using Nuxt's built-in lazy-loading patterns to fix issues source
-
Focus on Web Vitals attribution data to pinpoint exact elements causing performance issues — LCP, INP, and CLS metrics come with detailed attribution so you can identify and optimize specific DOM elements rather than guessing source
-
Add crossorigin="anonymous" to external scripts in your audit recommendations — the module flags missing crossorigin attributes because they improve security and enable error reporting for third-party scripts source
-
Ignore style-only hydration diffs as these are false positives — v1.1.3 filters style serialization differences to reduce noise source
-
Disable the hydration feature if your app uses ssr: false — the module will still try to detect mismatches and generate warnings even though hydration never runs source
-
Include @nuxt/hints in the build transpile array if you encounter "#imports" resolution errors — some build configurations with custom Vite optimizeDeps or rollup settings require the module to be explicitly transpiled source
-
Use the hover-to-highlight and click-to-inspect DevTools features during debugging — these interactive diagnostics let you navigate directly to problematic elements and source files without manual searching source
