Pascal Baljet
@pascalbaljet.bsky.social
Husband of Esmée, dad of Loïs and Kate ❤️
Works at @laravel.com. Open-source enthusiast. Also builds inertiaui.com.
https://pinkary.com/@pascalbaljet
Thanks for sharing!
November 6, 2025 at 12:56 PM
Thanks for sharing!
I'll put it on the list!
October 28, 2025 at 6:20 PM
I'll put it on the list!
Everything can be found in the documentation! Have fun with the View Transitions, the possibilities are endless! 🚀
inertiajs.com
inertiajs.com
Inertia.js - The Modern Monolith
Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers.
inertiajs.com
October 28, 2025 at 5:19 PM
Everything can be found in the documentation! Have fun with the View Transitions, the possibilities are endless! 🚀
inertiajs.com
inertiajs.com
Lastly, there's a new 'future' object where you can opt in to features that will become defaults in the next major release. Two examples:
✅ Opt in to the new <Dialog> element for error modals
✅ Let the <Head> component use the 'data-inertia' attribute instead of 'inertia'
✅ Opt in to the new <Dialog> element for error modals
✅ Let the <Head> component use the 'data-inertia' attribute instead of 'inertia'
October 28, 2025 at 5:19 PM
Lastly, there's a new 'future' object where you can opt in to features that will become defaults in the next major release. Two examples:
✅ Opt in to the new <Dialog> element for error modals
✅ Let the <Head> component use the 'data-inertia' attribute instead of 'inertia'
✅ Opt in to the new <Dialog> element for error modals
✅ Let the <Head> component use the 'data-inertia' attribute instead of 'inertia'
Next, you can pass a callback to provide defaults for all visits 🔗
This callback receives the URL and options for the visit, and returns an object with options to merge in. Perfect for enabling View Transitions globally, for example 😉
This callback receives the URL and options for the visit, and returns an object with options to merge in. Perfect for enabling View Transitions globally, for example 😉
October 28, 2025 at 5:19 PM
Next, you can pass a callback to provide defaults for all visits 🔗
This callback receives the URL and options for the visit, and returns an object with options to merge in. Perfect for enabling View Transitions globally, for example 😉
This callback receives the URL and options for the visit, and returns an object with options to merge in. Perfect for enabling View Transitions globally, for example 😉
You can pass defaults to createInertiaApp(), and even update them at runtime. There are three categories for now.
First, you can override some defaults that were previously hardcoded, such as the default prefetch cache duration or the 'recentlySuccessful' duration in forms ⏳
First, you can override some defaults that were previously hardcoded, such as the default prefetch cache duration or the 'recentlySuccessful' duration in forms ⏳
October 28, 2025 at 5:19 PM
You can pass defaults to createInertiaApp(), and even update them at runtime. There are three categories for now.
First, you can override some defaults that were previously hardcoded, such as the default prefetch cache duration or the 'recentlySuccessful' duration in forms ⏳
First, you can override some defaults that were previously hardcoded, such as the default prefetch cache duration or the 'recentlySuccessful' duration in forms ⏳
You can enable it *per visit* using the <Link> component or the router, but you can also enable it globally, which brings me to the next new feature.
We're introducing a way to set global defaults for Inertia! 🙌
We're introducing a way to set global defaults for Inertia! 🙌
October 28, 2025 at 5:19 PM
You can enable it *per visit* using the <Link> component or the router, but you can also enable it globally, which brings me to the next new feature.
We're introducing a way to set global defaults for Inertia! 🙌
We're introducing a way to set global defaults for Inertia! 🙌
Using a cn() / tw() helper to prefix all classes in the package won't work, as Tailwind still can't detect them that way.
October 27, 2025 at 9:37 PM
Using a cn() / tw() helper to prefix all classes in the package won't work, as Tailwind still can't detect them that way.
You can chain multiple method calls, pass an array with several merge paths, or even use a key-value array if you want to use the 'match existing items' feature on multiple paths 🧩
All of this is in the docs! Enjoy! 📚
All of this is in the docs! Enjoy! 📚
October 9, 2025 at 8:43 PM
You can chain multiple method calls, pass an array with several merge paths, or even use a key-value array if you want to use the 'match existing items' feature on multiple paths 🧩
All of this is in the docs! Enjoy! 📚
All of this is in the docs! Enjoy! 📚
And lastly, a big one: huge improvements to merging props! 💪
It's a new middle ground between merge() and deepMerge() that gives you precise control over how props are merged.
You can now prepend props, and even specify multiple merge paths, including nested ones.
It's a new middle ground between merge() and deepMerge() that gives you precise control over how props are merged.
You can now prepend props, and even specify multiple merge paths, including nested ones.
October 9, 2025 at 8:43 PM
And lastly, a big one: huge improvements to merging props! 💪
It's a new middle ground between merge() and deepMerge() that gives you precise control over how props are merged.
You can now prepend props, and even specify multiple merge paths, including nested ones.
It's a new middle ground between merge() and deepMerge() that gives you precise control over how props are merged.
You can now prepend props, and even specify multiple merge paths, including nested ones.
One awesome feature introduced in Inertia 2.0 was Client-Side Visits. It lets you update the URL, props, component, etc. without making a server request.
To reduce some boilerplate, there are now several handy shortcuts to update a page prop 🪄
To reduce some boilerplate, there are now several handy shortcuts to update a page prop 🪄
October 9, 2025 at 8:43 PM
One awesome feature introduced in Inertia 2.0 was Client-Side Visits. It lets you update the URL, props, component, etc. without making a server request.
To reduce some boilerplate, there are now several handy shortcuts to update a page prop 🪄
To reduce some boilerplate, there are now several handy shortcuts to update a page prop 🪄
This component is super configurable and customizable.
You can set the loading threshold, provide a default loading indicator, provide custom trigger elements, use scroll containers, get programmatic access, and more!
The docs are extensive, so be sure to check them out! 📖
You can set the loading threshold, provide a default loading indicator, provide custom trigger elements, use scroll containers, get programmatic access, and more!
The docs are extensive, so be sure to check them out! 📖
September 29, 2025 at 6:23 PM
This component is super configurable and customizable.
You can set the loading threshold, provide a default loading indicator, provide custom trigger elements, use scroll containers, get programmatic access, and more!
The docs are extensive, so be sure to check them out! 📖
You can set the loading threshold, provide a default loading indicator, provide custom trigger elements, use scroll containers, get programmatic access, and more!
The docs are extensive, so be sure to check them out! 📖
Besides automatic loading, you can also use manual mode so you can provide your own interface to load more items, like a "Load More" button.
You may even choose to switch to manual after a certain number of automatic loads 👌
You may even choose to switch to manual after a certain number of automatic loads 👌
September 29, 2025 at 6:23 PM
Besides automatic loading, you can also use manual mode so you can provide your own interface to load more items, like a "Load More" button.
You may even choose to switch to manual after a certain number of automatic loads 👌
You may even choose to switch to manual after a certain number of automatic loads 👌