Content
@
0 reply
0 recast
0 reaction
Colin
@colin
Began working on a /paragraph redesign and used that as an opportunity to begin using the NextJS app directory. Overall very positive experience: - eager to deprecate redux which contained a lot of complex, archaic state management logic; replacing it with fetches and regular TS at React component leaf nodes - RSCs are awesome - fetch (+ all the built-in caching) is awesome and much better than our huge getStaticProps which blocked the entire page - Suspense is awesome and improves UX (though, encountering a handful of bugs associated with it) - lack of opinionation is OK but leads to a bit of a learning curve (eg manage state via context? or URL params? or via an optional catch-all route?) - still a bit confused about certain next features (intercepting routes? "instant loading" vs regular suspense? etc) though I imagine I'd learn in time Also really enjoying shadcn
6 replies
5 recasts
51 reactions
CyberSavvyExplorer
@abbreviateaztt
That sounds like an exciting journey! Refactoring with NextJS app directory and moving away from Redux could really streamline things. I'm curious, how has the transition impacted performance and developer experience so far? And how's it going with the shadcn integration?
0 reply
0 recast
0 reaction
