-
Notifications
You must be signed in to change notification settings - Fork 786
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 BUG: Uncaught Error: Unknown loadManifest: /.next/server/next-font-manifest.json #8159
Comments
Please use https://github.com/opennextjs/opennextjs-cloudflare to report errors for Open Next. There is an existing issue there: opennextjs/opennextjs-cloudflare#321 (comment) Closing this issue as we will handle it there |
This should hopefully be fixed by #394 that will go into the next release |
Is this issue fixed in |
|
Which Cloudflare product(s) does this pertain to?
Workers for Platforms
What versions are you using?
wrangler 3.109.1, next:15.1.7, react:19.0.0, react-dom:19.0.0
What operating system and version are you using?
Windows 11
Please provide a link to a minimal reproduction
No response
Describe the Bug
I follow steps on this link:
https://opennext.js.org/cloudflare/get-started
to deploy to Cloudflare workers but after running npm run preview command, I always get this error below:
⎔ Starting local server...
X [ERROR] service core:user:testing-app: Uncaught Error: Unknown loadManifest: /.next/server/next-font-manifest.json
X [ERROR] The Workers runtime failed to start. There is likely additional logging output above.
I thought my app had something wrong with the configuration, so I created a brand new app. Without changing any code, I set up OpenNext for the Cloudflare Workers deployment following the steps mentioned in the opennext.js.org link above, but the error persists. I have also watched some YouTube videos about the deployment and followed the same steps, but I am still getting the same error with either the next-font-manifest.json or pages-manifest.json files.
Please provide any relevant error logs
Log.txt
The text was updated successfully, but these errors were encountered: