Our great sponsors
-
next-optimized-images
🌅 next-optimized-images automatically optimizes images used in next.js projects (jpeg, png, svg, webp and gif).
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
microsite
Do more with less JavaScript. Microsite is a smarter, performance-obsessed static site generator powered by Preact and Snowpack.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
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.
>Running a custom server means no deploying to Vercel. I understand that one the most, since Vercel has decided to lean on serverless
For those who want simple serverless deployment, but don't want to vendor lock in with Vercel, checkout serverless-next.js, it makes deploying to aws lambda@edge directly a breeze, it's awesome![1].
The catch is that this is intentionally made inconvenient. If it were a config setting I could just put it there,commit, and forget about it.
By making me setting an environment variable you are forcing me to remember to set it up in my infrastructure, on each environment, on each developer laptop, for each project independently, and if my project is open source, good luck with any user remembering/caring to set the env var.
And this is pretty intentional so that people forget or just don't care to disable it.
That's the catch.