fix(deps): bump nuxt from 2.16.2 to 3.3.1

[dependabot]

Bumps nuxt from 2.16.2 to 3.3.1.

Release notes

Sourced from nuxt's releases.

v3.3.1

3.3.0 is a minor (feature) release with lots of new features to play with. 3.3.1 was a swiftly following release to patch an issue with nuxi on Windows.

👀 Highlights

✨ Local module development DX

We've landed a raft of changes to enable local modules and improve DX. We now auto-scan your ~/modules folder and register top level files there as modules in your project (nuxt/nuxt#19394). When these files are changed, we'll automatically restart the nuxt server.

  export default defineNuxtConfig({
    modules: [
      '@nuxtjs/tailwindcss',
-     '~/modules/purge-comments'
    ]
  })

We also now expose nuxt/kit for easy access to kit composables in your local project without having to install @nuxt/kit (nuxt/nuxt#19422).

♻️ Restarting Nuxt

You can add files to the watch array to automatically restart the server (nuxt/nuxt#19530). This is likely to be particularly useful for module authors. You can also trigger a restart of the Nuxt server with the new restart hook (nuxt/nuxt#19084). We also landed a couple of fixes on restarting the Nuxt server which should improve your experience when developing.

🔥 Performance improvements

We've increased static asset maxAge to 1yr as a matter of best practice (nuxt/nuxt#19335), and support tree-shaking more of your build (nuxt/nuxt#19508). We also now support preloading <NuxtLink>s with a route in object-syntax (nuxt/nuxt#19120).

We also track how long it takes each module you use to perform its setup, and warn if it takes too long. You can see all these values by running your dev server with DEBUG=1

You can also opt-in to some of Nuxt's internal optimisations by configuring composables to be treeshaken in a particular environment (nuxt/nuxt#19383), or to have magic keys automatically injected (nuxt/nuxt#19490) - primarily useful for module authors.

🐛 Error handling

We now handle chunk errors by default (nuxt/nuxt#19086), meaning if your site updates with a redeploy, we automatically handle reloading it on navigation. You can disable this and handle it yourself with the new reloadNuxtApp composable. You can also set experimental.restoreState to preserve some of your app state across reloads.

We also have a new experimental error handling component: <NuxtClientFallback> (nuxt/framework#8216) which can capture errors rendering on server, replace them with fallback content, and granularly trigger rerendering the part with an error on the client. This can be enabled with experimental.clientFallback - feedback very welcome!

⚡️ Head improvements

We've migrated to use unhead directly (nuxt/nuxt#19519) - and automatically tree-shake server-only head composables like useServerHead from your client build (nuxt/nuxt#19576), meaning you can have great SEO without needing to include meta tag logic that's relevant only for crawlers in your client build.

There's also a new useHeadSafe composable that handles santising untrusted user input (nuxt/nuxt#19548).

🪵 Better logging in browser DevTools

Working with the Chrome DevTools team, we've landed a couple of features across the unjs + Nuxt ecosystem meaning we now have first-class support for hiding Nuxt internal stack traces from logs in your (Chromium-based, for now) browser (nuxt/nuxt#19243). We also landed a couple of improvements with stacktraces involving Nuxt hooks (unjs/hookable#69 and unjs/hookable#68) implementing console.createTask.

... (truncated)

Commits

• 184d57b v3.3.1
• e68a23a docs: improve head section (#19673)
• a169172 fix(nuxt): import builder path as file url
• 01ee5bd fix(nuxi): use file url to start nuxi (#19676)
• 2ebf5f4 v3.3.0 (#19524)
• 4b2cb52 fix(nuxt): fix default injection type for plugins (#19669)
• 9d850a2 feat(nuxt): add nitro:build:public-assets hook (#19638)
• 88a5f38 chore: constrain nitro to minor version
• 0f6276d fix(nuxt): mark non-augmented NuxtApp properties as unknown (#19643)
• e84ec61 feat(nuxt): support app config for server routes (#19489)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)