You're viewing the Inertia.js v2.0 documentation. Upgrade guide →
In addition to creating links, it's also possible to manually make Inertia visits / requests programmatically via JavaScript. This is accomplished via the router.visit()
method.
import { router } from '@inertiajs/vue3'
router.visit(url, {
method: 'get',
data: {},
replace: false,
preserveState: false,
preserveScroll: false,
only: [],
except: [],
headers: {},
errorBag: null,
forceFormData: false,
queryStringArrayFormat: 'brackets',
async: false,
showProgress: true,
fresh: false,
reset: [],
preserveUrl: false,
prefetch: false,
onCancelToken: cancelToken => {},
onCancel: () => {},
onBefore: visit => {},
onStart: visit => {},
onProgress: progress => {},
onSuccess: page => {},
onError: errors => {},
onFinish: visit => {},
onPrefetching: () => {},
onPrefetched: () => {},
})
However, it's generally more convenient to use one of Inertia's shortcut request methods. These methods share all the same options as router.visit()
.
import { router } from '@inertiajs/vue3'
router.get(url, data, options)
router.post(url, data, options)
router.put(url, data, options)
router.patch(url, data, options)
router.delete(url, options)
router.reload(options) // Uses the current URL
The reload()
method is a convenient, shorthand method that automatically visits the current page with preserveState
and preserveScroll
both set to true
, making it the perfect method to invoke when you just want to reload the current page's data.
When making manual visits, you may use the method
option to set the request's HTTP method to get
, post
, put
, patch
or delete
. The default method is get
.
import { router } from '@inertiajs/vue3'
router.visit(url, { method: 'post' })
put
or patch
is not supported in Laravel. Instead, make the request via post
, including a _method
field set to put
or patch
. This is called form method spoofing.You may use the data
option to add data to the request.
import { router } from '@inertiajs/vue3'
router.visit('/users', {
method: 'post',
data: {
name: 'John Doe',
email: 'john.doe@example.com',
},
})
For convenience, the get()
, post()
, put()
, and patch()
methods all accept data
as their second argument.
import { router } from '@inertiajs/vue3'
router.post('/users', {
name: 'John Doe',
email: 'john.doe@example.com',
})
The headers
option allows you to add custom headers to a request.
import { router } from '@inertiajs/vue3'
router.post('/users', data, {
headers: {
'Custom-Header': 'value',
},
})
When making visits / requests that include files, Inertia will automatically convert the request data into a FormData
object. If you would like the request to always use a FormData
object, you may use the forceFormData
option.
import { router } from '@inertiajs/vue3'
router.post('/companies', data, {
forceFormData: true,
})
For more information on uploading files, please consult the dedicated file uploads documentation.
When making visits, Inertia automatically adds a new entry into the browser history. However, it's also possible to replace the current history entry by setting the replace
option to true
.
import { router } from '@inertiajs/vue3'
router.get('/users', { search: 'John' }, { replace: true })
replace
to true
.You can use the router.push
and router.replace
method to make client-side visits. This method is useful when you want to update the browser's history without making a server request.
import { router } from '@inertiajs/vue3'
router.push({
url: '/users',
component: 'Users',
props: { search: 'John' },
clearHistory: false,
encryptHistory: false,
preserveScroll: false,
preserveState: false,
})
All of the parameters are optional. By default, all passed paramaters will be merged with the current page. This means you are responsible for overriding the current page's URL, component, and props.
If you need access to the current page's props you can pass a function to the props option. This function will receive the current page's props as an argument and should return the new props.
import { router } from '@inertiajs/vue3'
router.push({ url: '/users', component: 'Users' })
router.replace({
props: (currentProps) => ({ ...currentProps, search: 'John' })
})
By default, page visits to the same page create a fresh page component instance. This causes any local state, such as form inputs, scroll positions, and focus states to be lost.
However, in some situations, it's necessary to preserve the page component state. For example, when submitting a form, you need to preserve your form data in the event that form validation fails on the server.
For this reason, the post
, put
, patch
, delete
, and reload
methods all set the preserveState
option to true
by default.
You can instruct Inertia to preserve the component's state when using the get
method by setting the preserveState
option to true
.
import { router } from '@inertiajs/vue3'
router.get('/users', { search: 'John' }, { preserveState: true })
If you'd like to only preserve state if the response includes validation errors, set the preserveState
option to "errors".
import { router } from '@inertiajs/vue3'
router.get('/users', { search: 'John' }, { preserveState: 'errors' })
You can also lazily evaluate the preserveState
option based on the response by providing a callback.
import { router } from '@inertiajs/vue3'
router.post('/users', data, {
preserveState: (page) => page.props.someProp === 'value',
})
When navigating between pages, Inertia mimics default browser behavior by automatically resetting the scroll position of the document body (as well as any scroll regions you've defined) back to the top of the page.
You can disable this behavior by setting the preserveScroll
option to false
.
import { router } from '@inertiajs/vue3'
router.visit(url, { preserveScroll: false })
If you'd like to only preserve the scroll position if the response includes validation errors, set the preserveScroll
option to "errors".
import { router } from '@inertiajs/vue3'
router.visit(url, { preserveScroll: 'errors' })
You can also lazily evaluate the preserveScroll
option based on the response by providing a callback.
import { router } from '@inertiajs/vue3'
router.post('/users', data, {
preserveScroll: (page) => page.props.someProp === 'value',
})
For more information regarding this feature, please consult the scroll management documentation.
The only
option allows you to request a subset of the props (data) from the server on subsequent visits to the same page, thus making your application more efficient since it does not need to retrieve data that the page is not interested in refreshing.
import { router } from '@inertiajs/vue3'
router.visit('/users', { search: 'John' }, { only: ['users'] })
For more information on this feature, please consult the partial reloads documentation.
You can cancel a visit using a cancel token, which Inertia automatically generates and provides via the onCancelToken()
callback prior to making the visit.
import { router } from '@inertiajs/vue3'
router.post('/users', data, {
onCancelToken: (cancelToken) => (this.cancelToken = cancelToken),
})
// Cancel the visit...
this.cancelToken.cancel()
The onCancel()
and onFinish()
event callbacks will be executed when a visit is cancelled.
In addition to Inertia's global events, Inertia also provides a number of per-visit event callbacks.
import { router } from '@inertiajs/vue3'
router.post('/users', data, {
onBefore: (visit) => {},
onStart: (visit) => {},
onProgress: (progress) => {},
onSuccess: (page) => {},
onError: (errors) => {},
onCancel: () => {},
onFinish: visit => {},
onPrefetching: () => {},
onPrefetched: () => {},
})
Returning false
from the onBefore()
callback will cause the visit to be cancelled.
import { router } from '@inertiajs/vue3'
router.delete(`/users/${user.id}`, {
onBefore: () => confirm('Are you sure you want to delete this user?'),
})
It's also possible to return a promise from the onSuccess()
and onError()
callbacks. When doing so, the "finish" event will be delayed until the promise has resolved.
import { router } from '@inertiajs/vue3'
router.post(url, {
onSuccess: () => {
return Promise.all([
this.doThing(),
this.doAnotherThing()
])
}
onFinish: visit => {
// This won't be called until doThing()
// and doAnotherThing() have finished.
},
})