![]() We've also added a test suite to cover these layer resolution changes.Īnd probably one of the most significant changes - if you are using remote layers we now clone these within your node_modules/ folder ( #109 ) so layers can use dependencies with your project. ![]() This should mean you can rely on utilities that layers may inject. We now more carefully load layer plugins ( #22889 and #23148 ) and middleware ( #22925 and #23552 ) in the order of the layers, always loading your own plugins and middleware last. Timeout : 100 } } } } ) □ Layer improvements We now support scanning layouts within subfolders in ~/layouts in the same way as we do with ~/components. □ This is a behaviour change so do take care with this one: □ We would definitely advise using if you're using images in your site it can apply optimisations to make your site more performant. We've now made and first-class built-in components, documenting them and auto-installing the first time that they are used ( #23717 ). ![]() □ You can check out the release notes for more information - and stay tuned for an article detailing our roadmap for the future. Nuxt DevTools v1.0.0 is out and we now think it's ready to be shipped as a direct dependency of Nuxt. (For example, we now share the same port with the Vite websocket, meaning better support for docker containers in development.) □ Built-in Nuxt DevTools ![]() There are some exciting improvements there to follow, so do check out the latest releases. Just to remind you, we're now using the new Nuxt CLI which is now versioned separately. We have a lot of exciting features in v3.8, and can't wait for you to try it out. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |