docs/3.guide/2.best-practices/performance.md (2)

115-124:Consider showing how to destructure or access the returned data.

The example returns an array fromPromise.all, sodata will contain[products, shoes]. For clarity, you might want to show destructuring or accessing individual results:

const{ data}=awaituseAsyncData(()=>{returnPromise.all([$fetch("/api/products/"),$fetch("/api/category/shoes")]);});// data will be [productsArray, shoesArray]// Or destructure: const [products, shoes] = data.value

This helps readers understand the structure of the returned data immediately.

---

115-124:Document error-handling expectations for Promise.all.

While the example is correct, it's worth noting in the surrounding prose (or as an inline comment) that if any API call rejects, the entirePromise.all fails. For production code, consider mentioning alternatives likePromise.allSettled when partial failures are acceptable.

This addition strengthens the "best practices" aspect of the guide without complicating the basic example.

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Learnt from: TofandelRepo: nuxt/nuxt PR: 33192File: test/nuxt/use-async-data.test.ts:366-373Timestamp: 2025-09-10T14:42:56.647ZLearning: In the Nuxt useAsyncData test "should watch params deeply in a non synchronous way", the foo watcher intentionally updates both params.foo and params.locale using locale.value, simulating a scenario where one watcher consolidates multiple reactive values into a shared params object for testing debounced/non-synchronous behavior.