Given the most recent attempt to migrate Volt 2 to Next 13's app router, felt we should move this back to Trial. Thoughts on this can be read in this Slack thread.
TLDR: Next.js pages router works great for us, without gotchas or perceivable problems. Yet, moving to the new app router involves a lot of friction. To recommend Next.js as Adopt would, I think, also imply that we're on board with Next.js 13's new router, react server components (RSC) and more.
As adopting this would come at a significant cost to Artsy due to Palette not being compatible (Palette requires a JS runtime to function), this should give us pause. Moving from Trial -> Adopt requires more discussion.
Given the most recent attempt to migrate Volt 2 to Next 13's app router, felt we should move this back to Trial. Thoughts on this can be read in this Slack thread.
TLDR: Next.js pages router works great for us, without gotchas or perceivable problems. Yet, moving to the new app router involves a lot of friction. To recommend Next.js as
Adoptwould, I think, also imply that we're on board with Next.js 13's new router, react server components (RSC) and more.As adopting this would come at a significant cost to Artsy due to Palette not being compatible (Palette requires a JS runtime to function), this should give us pause. Moving from
Trial->Adoptrequires more discussion.