next-optimized-images VS serverless-next.js

Same. I found this example [1] particularly helpful, although I don't know how good this [2] library it uses is. Overall, I've seen multiple OSS projects [3] that try to support a missing functionality in Next.js seem to just give up trying to keep up with their breaking changes.

[1] https://stackblitz.com/edit/github-mwzv1t?file=README.md

[2] https://github.com/hoangvvo/next-connect

[3] https://github.com/cyrilwanner/next-optimized-images

But yes, it felt more finnicky if that makes sense. I'd suggest building your own image thing using next-optimised-images to suit your exact preferences. You can generate a blurred low res image, a higher res version and overlap them together to essentially re-create a lite version of Image component : https://github.com/cyrilwanner/next-optimized-images

Next.js component is not supported (see Next.js Image loader). Use img instead. The sample project is already set up to use next-optimized-images which can instead be used to serve images.

next-optimized-images

next.js actually does images even better in my experience, There's no magical Gatsby Image plugin but you can use next-optimized-images which will give you all the raw materials such as traced SVGs, etc and you can build your own image component around that very easily which you have full style control over.

We aren't using anything at the moment but you can use for example https://github.com/cyrilwanner/next-optimized-images

That's why I removed next/image and ended up using https://github.com/cyrilwanner/next-optimized-images

That lets you export the images pre-optimized for different sizes/etc. You can then do a normal next export.

You can still use `next/image` when outputting a static site, as long as you use `next start`. Using `next export` removes the server entirely, meaning you can't optimize images on demand.

There's an open issue to explore optimizing images at build time, but for now, you can use https://github.com/cyrilwanner/next-optimized-images

TheVECentre.com is predominately built using Next.js and Tailwind CSS. Two Next.js plugins, next-seo and next-optimized-images, to handle the SEO orientated properties and optimise images for different device sizes respectively. Additionally, React Icons supplies any social icons, EmailJS powers the contact form and Framer Motion adds animations to the site.

I like your style 😎 Im using next.js for incremental static regeneration . I've been going down rabbit hole after rabbit hole regarding image optization. I found this, https://github.com/cyrilwanner/next-optimized-images .

I'm currently waiting SST v2 to be released where they will use https://open-next.js.org instead of https://github.com/serverless-nextjs/serverless-next.js

To deploy the app, I had the requirement to use AWS as a cloud-provider, with a limited budget, so neither Vercel (a safe choice, as it is the company which develops Next.js), nor a containerized solution like the managed AWS ECS Fargate service could satisfy my needs. Then, I started with a serverless hosting thanks to the serverless-next project, which provides a serverless plugin or a CDK construct to deploy a Next.js stack. However, this project is no more well-maintained and new Next.js features (like middlewares, etc.) are not supported.

If you have the time and resources, I'd suggest to take a look at SST.dev and or OpenNext (created by the SST people). With that ISR should work (although they still seem to work on upgrading to v12). Or take a look at https://github.com/sladg/nextjs-lambda to run NextJS on a lambda exclusively.

serverlessnextjs does not support NextJS 13. https://github.com/serverless-nextjs/serverless-next.js/issues/2497

I hate Amplify. I've been using it for around 2 weeks, because serverless-next.js no longer works with Next v13.

Let's mention that it's possible to deploy a Next.js application using SST 😅. This setup relies on the serverless-next.js project and it's hidden behind a construct named NextJsSite. It can be a very efficient solution when you want to ship your application on AWS environment (I use it for a production workload in my current company).

ATM Next JS is SSR (Server Side Rendering) so only S3 and CloudFront is not enough! As mentioned here already Lambda@Edge can do the server parts and is used like in Amplify. An Alternative would the serverless framework which offers a next js deployment https://github.com/serverless-nextjs/serverless-next.js .