Does NextJS have the concept of a resolver? Is the Suspense paradigm their solution to the issue?
Unanswered
Gharial posted this in #help-forum
GharialOP
I'm in the process of learning NextJS atm and have had experience with Angular and SvelteKit. In Angular they had the concept of being able to resolve (fetch and on success route forward and if not 404) data prior to entering a route. In SvelteKit you could call your data in
layout/page.ts and use it in the related layout/page.svelte file and its children. Does NextJS have a similar paradigm or is the suggested way of handling slow api requests to create ComponentSkeletons while in Suspense?