@nuxt/docs-nightly 4.0.0-29119536.fadd618d → 4.0.0-29119630.0b55bf72
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -610,7 +610,7 @@ onMounted(() => console.log(document.cookie))
|
|
|
610
610
|
</script>
|
|
611
611
|
```
|
|
612
612
|
|
|
613
|
-
## Options API
|
|
613
|
+
## Options API Support
|
|
614
614
|
|
|
615
615
|
Nuxt provides a way to perform `asyncData` fetching within the Options API. You must wrap your component definition within `defineNuxtComponent` for this to work.
|
|
616
616
|
|
|
@@ -744,7 +744,7 @@ const { data } = await useFetch('/api/superjson', {
|
|
|
744
744
|
|
|
745
745
|
## Recipes
|
|
746
746
|
|
|
747
|
-
### Consuming SSE (Server
|
|
747
|
+
### Consuming SSE (Server-Sent Events) via POST request
|
|
748
748
|
|
|
749
749
|
::tip
|
|
750
750
|
If you're consuming SSE via GET request, you can use [`EventSource`](https://developer.mozilla.org/en-US/docs/Web/API/EventSource) or VueUse composable [`useEventSource`](https://vueuse.org/core/useEventSource/).
|
|
@@ -659,7 +659,7 @@ These aliases were removed, for greater clarity.
|
|
|
659
659
|
|
|
660
660
|
The issue came up when adding `dedupe` as an option to `useAsyncData`, and we removed the boolean values as they ended up being _opposites_.
|
|
661
661
|
|
|
662
|
-
`refresh({ dedupe: false })` meant
|
|
662
|
+
`refresh({ dedupe: false })` meant **do not _cancel_ existing requests in favour of this new one**. But passing `dedupe: true` within the options of `useAsyncData` means **do not make any new requests if there is an existing pending request.** (See [PR](https://github.com/nuxt/nuxt/pull/24564#pullrequestreview-1764584361).)
|
|
663
663
|
|
|
664
664
|
#### Migration Steps
|
|
665
665
|
|