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]: middleware-manifest.json not found #1267
Comments
OP here, thank you for the continued support! The OS is Windows 11. I'll also confirm that no files are missing from the repo, and adding back the .next folder didn't fix the issue. |
+1 |
Closing as resolved, as per the forum post. This was due to an incompatibility between Next 11 and an older version of the runtime, which I believe is resolved with later versions because we have no recent reports. |
Just stop terminal (ctrl + c) and in explorer right click on .next folder and delete it. After that run program again. Next build again with new middleware-manifest.json. For me it works fine :) |
Thank you, help a lot |
Still an issue in next@14.2.0-canary.48:
|
Summary
It appears that for a site that's not using Middlewares at all, we're still looking for a
middleware-manifest.json
file and this is causing errors to load the site altogether.A user reported this on the forums: https://answers.netlify.com/t/53484
As per our sync yesterday, we're still not sure about the exact cause of this issue, so this might need some further investigation.
Steps to reproduce
Try visiting their website here: https://naughty-varahamihira-fcffe0.netlify.app/
A link to a reproduction repository
https://github.com/GabZanMacaw/napoleontest
Plugin version
4.2.7
More information about your build
netlify.toml
)What OS are you using?
No response
Your netlify.toml file
None in repo
Your public/_redirects file
None in repo
Your
next.config.js
file`next.config.js`
Builds logs (or link to your logs)
https://app.netlify.com/sites/naughty-varahamihira-fcffe0/deploys/6230a45e1f405520c81e1d71
Function logs
Function logs
.next JSON files
No response
The text was updated successfully, but these errors were encountered: