ERROR: Unknown functions manifest version. Expected 3 but found 4

[Anietz]

This build error affects both old and new deployment. Attached a screenshot.

[dario-piotrowicz]

Hi @Anietz, thank you very much for the issues

But I am not able to reproduce this, could you please provide more details? Like what next.js version you're using, what vercel cli version you have, what your code does (only static, uses app dir, etc...), and whatever else you think could be related to the issue.

If possible, if you could provide the code itself in a repo or something that would be extremely helpful 🙏

[mistermantas]

Also experiencing this on cf pages

▲ Detected Next.js version: 12.1.4
Node is v16.15.1

Problem seems to be the versions, in the docs I missed out that:

Next.js requires Node.js v12.22.0 or later to build successfully. To set your Node version, go to Settings in your Workers project > Environment Variables (advanced) section and add a NODE_VERSION variable with a value of 12.22.0 or greater.

not a logical default for cf pages to use a version that doesn't immediately build, I think...

also see - #40

[dario-piotrowicz]

not a logical default for cf pages to use a version that doesn't immediately build, I think...

yeah... hopefully it'll change at some point soon-ish: cloudflare/pages-build-image#1

[dario-piotrowicz]

▲ Detected Next.js version: 12.1.4

Sorry could you clarify? is this the log you see on Pages? (and I assume you're using 16.15.1 locally?) have you then changed/set your NODE_VERSION in the dashboard?

[mistermantas]

▲ Detected Next.js version: 12.1.4

Sorry could you clarify? is this the log you see on Pages? (and I assume you're using 16.15.1 locally?) have you then changed/set your NODE_VERSION in the dashboard?

it is the log from Pages and that was the version of Node I was using in Pages. I had set an env variable for NODE_VERSION but not NEXT_VERSION - setting both fixed the issue as I said

[dario-piotrowicz]

sorry I misread the log and thought you were getting two different node versions 😓 (one locally and one from pages)

[dario-piotrowicz]

I am not sure I know this NEXT_VERSION env variable and what it is used for 😕

anyways, if I understand correctly, are things working and this issue can be closed? 🙂

[Anietz]

@dario-piotrowicz I am using NODE_VERSION 16.13.0 and NEXT_VERSION 12.1.4.
Setting this values on the dashboard seems not to fix the issue

[dario-piotrowicz]

@Anietz I'd want to look more into this but as I mentioned I could not reproduce the issue, could you please help me with some more details? some reproduction steps? or even some code? that would be extremely helpful 🙏

[Anietz]

@dario-piotrowicz I see that when I changed the build config on the dashboard from npx @cloudflare/next-on-pages --experimental-minify to next build && next export it actually works.
I think this issue can be closed now

[dario-piotrowicz]

Glad to hear you've solved the issue 🙂

Just to make sure you're aware, next export is going to generate your app as a static site (so no SSR or edge bindings, etc...), hopefully this is what you want 🙂👍