inertia-vue-development

name: inertia-vue-development description: >- Develops Inertia.js v2 Vue client-side applications. Activates when creating Vue pages, forms, or navigation; using ,
, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions Vue with Inertia, Vue pages, Vue forms, or Vue navigation.

Inertia Vue Development

When to Apply

Activate this skill when:

Creating or modifying Vue page components for Inertia
Working with forms in Vue (using <Form> or useForm)
Implementing client-side navigation with <Link> or router
Using v2 features: deferred props, prefetching, or polling
Building Vue-specific features with the Inertia protocol

Documentation

Use search-docs for detailed Inertia v2 Vue patterns and documentation.

Basic Usage

Page Components Location

Vue page components should be placed in the resources/js/pages directory.

Page Component Structure

Important: Vue components must have a single root element.

Client-Side Navigation

Basic Link Component

Use <Link> for client-side navigation instead of traditional <a> tags:

Link with Method

Prefetching

Prefetch pages to improve perceived performance:

Programmatic Navigation

Form Handling

`useForm` Composable

For Inertia v2.0.x: Build forms using the useForm composable as the <Form> component is not available until v2.1.0+.

Inertia v2 Features

Deferred Props

Use deferred props to load data after initial page render:

Polling

Automatically refresh data at intervals:

WhenVisible (Infinite Scroll)

Load more data when user scrolls to a specific element:

Server-Side Patterns

Server-side patterns (Inertia::render, props, middleware) are covered in inertia-laravel guidelines.

Common Pitfalls

Using traditional <a> links instead of Inertia's <Link> component (breaks SPA behavior)
Forgetting that Vue components must have a single root element
Forgetting to add loading states (skeleton screens) when using deferred props
Not handling the undefined state of deferred props before data loads
Using <form> without preventing default submission (use <Form> component or @submit.prevent)
Forgetting to check if <Form> component is available in your Inertia version