NextJS - (v11) don't use Image components in conjunction with the `export` command.

#nextjs

So,

I'm rewriting this post. after I did some more reading and digging, and posting in my online programming community.

Gotta say, I'm pretty heart-broken over the NextJS framework.

With all it's bells an whistles, the stipulate in various places in their doc that the Image component is not supported in the next export command.

They do give some sort of inklink of a fix, by using custom loaders to solve this issue - but there is now example, no deep dive into how to implement such a solution.

I will try to implement such a solution myself, and will get back to you with some implementation.

Images on an SSR framework seem like such a fundamental thing.

Top comments (0)

Property-Based Testing in Rust: Finding Hidden Bugs with Random Inputs

Aarav Joshi - Mar 9

COURTROOM NO. 2 — THEO VS. UNIT TESTING: JUSTICE OR MISJUDGMENT?

Juan Blasco - Mar 9

Understanding JavaScript Objects and Internal Properties

Beatris Ilieva - Mar 9

TS1329: '{0}' accepts too few arguments to be used as a decorator here. Did you mean to call it first and write '@{0}()'?

Lior Amsalem - Mar 9

Youtube Tutorial Series 📺

So you built a Next.js app, but you need a clear view of the entire operation flow to be able to identify performance bottlenecks before you launch. But how do you get started? Get the essentials on tracing for Next.js from @nikolovlazar in this video series 👀

Watch the Youtube series

DEV Community