Nuxt 3 log.level constraints with internal module output

Global Log Level Behavior

Nuxt 3 provides a log.level configuration in nuxt.config.ts to manage console verbosity. By setting this to 'error' or 'fatal', developers can suppress info and warn messages to reduce noise during the build and development cycles.

Internal Module Consistency

While the global configuration affects the core framework and server middleware, there is uncertainty regarding how internal modules and third-party plugins handle these settings. Some modules may implement independent logging mechanisms that bypass the framework's centralized log level filter.

This creates a discrepancy where critical alerts are preserved, but non-essential warnings from specific modules continue to populate the console despite a restrictive global setting.

• Does the log.level configuration strictly enforce output limits across all internal Nuxt modules?
• Is there a documented method to force third-party module logs to adhere to the global log level?