Is it possible to integrate Next.js into this package?

[kmajay978]

The package is great, but we’ve noticed that none of our apps meet Shopify’s Built for Shopify (BFS) and LCP requirements using this repo. Despite extensive optimizations—such as using a CDN, image lazy loading, React lazy loading components, caching static content and more—we’re still not achieving the desired results.

I've seen others successfully meet BFS criteria using Remix or Next.js. It would be helpful if you could provide some insights on how to achieve this.

👍 → Migrate to Next.js + Express

Transitioning from Vite + React + Express to Express + Next.js.

[kinngh]

@kmajay978 this should've been a discussion in the first place, not an issue. Converted it.

Now,

1. Understand what LCP actually is instead of just going "Fuck it let's migrate because everyone else is saying that is what solved the issue"
2. Migrating to other frameworks isn't gonna help. You're looking for an easy way out instead of actually understanding how things work, which, on the long term is a terrible idea because you're gonna invest a lot of time into migration and then realize all of that time was wasted
3. there's no point in using Express with Next.js. Just use Nextjs in a node environment aka just host it on a server.
4. A deep dive into optimizing LCP from Google is a great video on what LCP is and how to optimize it.
5. Other things you want to do is cache and try different hosting providers

[kmajay978]

Hello @kinngh ,

Changing the current framework will likely take a considerable amount of time, based on my assumptions. Instead, I plan to use your [shopify-nextjs-prisma-app] repository and replace the Prisma database with MongoDB, as my existing database and structure are built on MongoDB.

Could you let me know if this is possible? If so, I'd appreciate any guidance on how to proceed and what steps are necessary to make it work.

[kinngh]

Prisma isn't a database, it's an ORM. You can use Prisma with MongoDB. Though you can still swap out Prisma entirely with Mongoose and still be good to go.

Also, I still don't understand the need to change frameworks - the problem with getting your opinion from Twitter (and Internet in general) is you're not forming your own opinions and hoping the change would magically make things better. Sure the DX could be better between frameworks because it comes down to personal preference, but just know that swapping from one framework to the other isn't the silver bullet you're looking for.

Like I said before, learn what LCP is and how to optimize it instead of hoping that a switch would work out.