Skip to content

default loader is not compatible with `next export #509

Discussion options

You must be logged in to vote

If you want to deploy on vercel, you wouldn't do next export since vercel has a server on the backend.

Basically, the Image tag from Next does some optimizations server side, so you need a server to run the app. next export exports your code to a static folder (aka, no server). It can't do that with non-static code.

What you can do is:

  1. Remove all references to the Image tag with some other image tag.
  2. Deploy to vercel without next export
  3. Fix the default loader (not sure why yours isn't working)

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by PatrickAlphaC
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants