In this video, I would like to just take a quick overview of some other changes within the Nuxt for Migration Guide that I think are worthy of note, because they might impact your Nuxt applications, or just because they are kind of interesting. So the first one here falls into that kind of interesting category, and that is the removal of experimental features. Specifically, four experimental features are no longer configurable in Nuxt 4. That is, the tree-shakeable client-only config schema, polyfill, view-use-head, and respect-no-ssr-head.
Also, the Veed dev-bumbler is no longer configurable, as it will use VeedNode by default. What's interesting to me about this is it marks some good progress. This is exactly what we want to see. We want to see...
experimental things solidify and then no longer become a variable in the equation. They just are how they are and Nuxt works consistently across different applications. This is great. Another change worthy of note is the removal of the window underscore Nuxt object after the app finishes hydration.
The reason that this is changing is because this opens a way to multi-app patterns and then enables us to focus on a single way to access Nuxt data, the use Nuxt app. underscore underscore Nuxt underscore underscore to access the payload or any other Nuxt global data, you should instead reach for use Nuxt app. Another change worth mentioning here, is a change to the directory index scanning. What's changed specifically?
Well, child folders inside of the middleware directory are now scanned for index files and are automatically registered as middleware in your project. So you can have these nicely organized nested middleware directories and the index file is picked up by default. This is how plugins already worked. So this change just makes the middleware folder consistent with the plugins folder.
The last change that I want to mention is the deduplication of route metadata. In Nuxt, it's possible to set some route metadata using the define page meta macro. Things such as the name and the path and so on. meta object.
Now they're only accessible in a single place. That is on the root route object instead of also nested down inside of meta. This video and the rest of this course has not covered all of the changes within this upgrade guide. There are a few other small things to take into account.
So go and check out the guide for yourself, but honestly at this point you shouldn't have much left to do.