nuxtApp.call

[pi0]

Describe the feature

Context: #14269 and #14723

While we try to restore context on best efforts, It is not always possible or convenient. There is an (intended to be internal) util callWithNuxt from #app can be used to use to restore context for async composables:

import { callWithNuxt } from '#app'

// unsupported transform context
const nuxtApp = useNuxtApp()
await something()
await callWithNuxt(navigateTo, ['/route', { replace: true }])

It is not convenient for DX because for performance reasons, we chose to accept second arg as arg array and that also it is not auto-imported. This utility is fundamentally bound to nuxtApp instance and can be exposed to public API:

const nuxtApp = useNuxtApp()
await something()
await nuxtApp.call(navigateTo, '/route', { replace: true })

Alternatives:

• We also have defineAsync to resolve issue but still there is no guarantee transform method works everyever.
• We have callWithNuxt which could be exposed as an auto import but it is not user friendly nor makes sense to use another auto import when nuxtApp is main context

Additional information

• Would you be willing to help implement this feature?
• Could this feature be implemented as a module?

Final checks

• Read the contribution guide.
• Check existing discussions and issues.

[antfu]

For reference, @posva proposed a similar concept for Vue core: vuejs/core#7451. I think we could align with the naming convention and maybe use it underneath later.

[danielroe]

Agreed. Might be worth waiting until the vue core PR is merged so we can align on the name.