fix: use console warn instead of useLogger

Signed-off-by: Pascal Sthamer <[email protected]>

src/runtime/nitro/plugins/50-updateCsp.ts

@@ -1,7 +1,6 @@
 import { defineNitroPlugin } from '#imports'
 import { resolveSecurityRules } from '../context'
 import type { ContentSecurityPolicyValue } from '../../../types/headers'
-import { useLogger } from '@nuxt/kit'
 
 /**
  * This plugin updates the CSP directives with the nonce and hashes generated by the server.
@@ -30,8 +29,6 @@ export default defineNitroPlugin((nitroApp) => {
 })
 
 function updateCspVariables(csp: ContentSecurityPolicyValue, nonce?: string, scriptHashes?: Set<string>, styleHashes?: Set<string>) {
-  const logger = useLogger('nuxt-security')
-
   const generatedCsp = <ContentSecurityPolicyValue>Object.fromEntries(Object.entries(csp).map(([directive, value]) => {
     // Return boolean values unchanged
     if (typeof value === 'boolean') {
@@ -42,7 +39,7 @@ function updateCspVariables(csp: ContentSecurityPolicyValue, nonce?: string, scr
     const modifiedSources = sources
       .filter(source => {
         if (source.startsWith("'nonce-") && source !== "'nonce-{{nonce}}'") {
-          logger.warn('Removing static nonce from CSP header.')
+          console.warn('[nuxt-security] removing static nonce from CSP header')
           return false
         }
         return true