day 63 - dived into Sequential Data Fetching in Next.js15 - basically when one request depends on another (fetch B needs data from fetch A) - slower (longer loading) but sometimes you just cannot avoid it #80DaysOfNextJS #NextJS15 #React #typeScript

coding_robin's tweet image. day 63

- dived into Sequential Data Fetching in Next.js15

- basically when one request depends on another (fetch B needs data from fetch A)

- slower (longer loading) but  sometimes you just cannot avoid it

#80DaysOfNextJS #NextJS15 #React #typeScript
coding_robin's tweet image. day 63

- dived into Sequential Data Fetching in Next.js15

- basically when one request depends on another (fetch B needs data from fetch A)

- slower (longer loading) but  sometimes you just cannot avoid it

#80DaysOfNextJS #NextJS15 #React #typeScript
coding_robin's tweet image. day 63

- dived into Sequential Data Fetching in Next.js15

- basically when one request depends on another (fetch B needs data from fetch A)

- slower (longer loading) but  sometimes you just cannot avoid it

#80DaysOfNextJS #NextJS15 #React #typeScript
coding_robin's tweet image. day 63

- dived into Sequential Data Fetching in Next.js15

- basically when one request depends on another (fetch B needs data from fetch A)

- slower (longer loading) but  sometimes you just cannot avoid it

#80DaysOfNextJS #NextJS15 #React #typeScript

- e.g. fetch all posts → then for each post, fetch author using userId - classic “one after the other” pattern - downside: if fetch A fails, fetch B does not even start #80DaysOfNextJS #NextJS15 #React #typeScript

coding_robin's tweet image. - e.g. fetch all posts → then for each post, fetch author using userId

- classic “one after the other” pattern

- downside: if fetch A fails, fetch B does not even start

#80DaysOfNextJS #NextJS15 #React #typeScript
coding_robin's tweet image. - e.g. fetch all posts → then for each post, fetch author using userId

- classic “one after the other” pattern

- downside: if fetch A fails, fetch B does not even start

#80DaysOfNextJS #NextJS15 #React #typeScript
coding_robin's tweet image. - e.g. fetch all posts → then for each post, fetch author using userId

- classic “one after the other” pattern

- downside: if fetch A fails, fetch B does not even start

#80DaysOfNextJS #NextJS15 #React #typeScript

United States Trends
Loading...

Something went wrong.


Something went wrong.