ReferenceError: File is not defined

[raphaelmans]

Summary

Fail on build

Error occurred prerendering page "/profile/hustler". Read more: https://nextjs.org/docs/messages/prerender-error
ReferenceError: File is not defined

> Export encountered errors on following paths:
        /(logged)/onboarding/business/page: /onboarding/business
        /(logged)/profile/business/page: /profile/business
        /(logged)/profile/hustler/page: /profile/hustler

Additional information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.4.0: Mon Mar  6 21:00:41 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T8103
Binaries:
  Node: 18.13.0
  npm: 8.19.3
  Yarn: 1.22.19
  pnpm: 8.6.12
Relevant Packages:
  next: 13.5.3
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: N/A

Example

No response

[ealexhaywood]

I was getting this error on a page that was using FormData and File, everything worked locally on next dev and next build && next start, but was failing when deploying to Vercel.

Upgrading to Node 20 fixed it

[vishnukumar89]

@ealexhaywood I have Node : v20.13.1. Still, I'm facing the same issue.

[netrolite]

thank you so much

[nduongg04]

thanks for your anwser

[btnalexandre]

thanks work like a charm !

[dragonfore4]

This work for me too , thanks

[devslife7]

I got the same error when deploying. It works great on my machine because I am running node 20x. Vercel deployment settings out of the box uses node 18x. So i went to vercel app settings and changed it to 20x, not it works like a charm.

[steinhardt21]

Also for me! Thank you!

[ahmadalfy]

Can confirm, migrating to Node 20 fixed the issue

[XoL1507]

tell ma. maybe i can help.

[smukideejeah]

I confirm.

[faustinozanetto]

I've encountered the same issue and I can confirm upgrading to Node 20 fixes it.

[softmarshmallow]

that was easy

[arjendevos]

I upped to v20 but still got the issue: File is not defined

[bascor1207]

The same issue occurred, and the same resolution applied. It was failing in my GitHub Actions, but upgrading to Node 20.x in main.yml solved the issue.

[henryobiaraije]

Upgrading to v20 solved this, even locally.