Types of changes

• Chore
• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Inludes (merge after):

• feat(node)!: upgrade to v20 #635

This updates the lockfile and adapts tests for the most recent Nuxt v3.

• There is one new link in head for Nuxt's build meta, so some test counts need to increase by one. New line looks like that:

  <link nonce="vK9riLzAB9wDjnrXlZiPg8Uk" integrity="sha384-0qI7x4Pjqjj0AeE8dIhQUTfElUp/2IMx8Vl8X/cREdyAfHNwpbKCxtpUHFbt5p8w" rel="preload" as="fetch" fetchpriority="low" crossorigin="anonymous" href="/_nuxt/builds/meta/test.json">

• One test checked a seemingly incorrect path which resulted in a 404 page being instead, this was likely unintended (I noticed because nitro now returns other headers now for error pages which made the test fail)
• the island logic does not work anymore, I concluded after long research: it appears the island renderer has its own context now and can't reuse the normal event context to check for an existing nonce, thus it generates a different nonce in html compared to the response's header. I disabled that test for now.
  • cc @huang-julien would you please confirm my observation? Is there any way to let nuxt-security generate just one nonce nowadays? relevant links
  • PR including the change to Nuxt: refactor(nuxt): move island renderer into its own event handler nuxt/nuxt#31386
  • check that doesn't work anymore: https://github.com/Baroshem/nuxt-security/pull/502/files#diff-08e3d6e6ad0ac48304338cb8d7a968879561981df0b6da0d565ca54d261447cbR10
  • previously available shared context property: https://github.com/nuxt/nuxt/blob/c0fb30d6d0f06a0c1160e20c9c8f819075d62b14/packages/nuxt/src/core/runtime/nitro/renderer.ts#L503

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes (if not applicable, please state why)