![]() ![]() This release ships with new Nitro 2.5, which has a whole list of exciting improvements that are worth checking out. You can find out more about how to update your code if this affects you in the original PR. NuxtApp (accessible now from NuxtPayload interface).This should improve type safety within Nuxt in a number of locations where unspecified types fell back to any: įinally, we have removed more locations where objects had a default any type. You should now also have type support for runtime Nitro hooks. So when importing from #imports in your server directory, you'll get IDE auto-completion for the right import locations in Nitro, and won't see Vue auto-imports like useFetch that are unavailable within your server routes. We now have better support for server-specific #imports and augmentations if you are using the new ~/server/tsconfig.json we shipped in Nuxt 3.5. It also unblocks use of Nuxt Image on Vercel (with more potential for automatic provider integration coming soon). So you should get the best of both worlds when deploying a site that doesn't require runtime SSR. This means we can configure any route rules (redirects/headers/etc) that do not require a server function. That means if you are deploying a static build (produced with nuxt generate) to a supported provider (currently vercel and netlify with cloudflare and github pages coming soon) we'll prerender your pages with special support for that provider. Up to now, running nuxt generate produced the same output on every deployment provider, but with Nuxt 3.6 we now enable static provider presets automatically. These will get passed through to the underlying DOM elements. To give you more fine-grained control over your page/layout components, for example to create custom transitions with GSAP or other libraries, we now allow you to set pageRef on and layoutRef on also should decrease your total bundle size.) We also include your error component JS in your main entrypoint, meaning that if an error occurs when a user has no connectivity, you can still handle it with your ~/error.vue. The first thing that happens when your app is hydrated is that your plugins run, and so we now perform build-time optimisations on your plugins, meaning they do not need to be normalised or reordered at runtime. You can completely disable this indicator by setting spaLoadingTemplate: false in your nuxt configuration file. ⡠By default an animated Nuxt icon is rendered. You can now place an HTML file in ~/app/spa-loading-template.html with some HTML you would like to use to render a loading screen that will be rendered until your app is hydrated on these pages. If your site is served with ssr: false or you have disabled server-rendering on some of your pages, you might be particularly interested in the new built-in SPA loading indicator. This minor release contains quite a lot, and we have big plans SPA loading indicator We're expecting an initial POC to take shape in the next month, and would very much appreciate community feedback on this. Three significant RFCs: Nuxt Font, Nuxt Assets and Nuxt Scripts. We are aiming to release this alongside Nuxt 3.7, but you would be very welcome to test and contribute to nuxi-ng before then! The open-sourcing of nuxt/cli by - a new, drop-in replacement for nuxi featuring more extensibility and better DX. ![]() In the coming week you can expect two announcements: 3.6.0 is the next minor release, packed with improvements and bug fixes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |