I found a similar topic on this forum here. I made some changes in NODE_VERSION varying from 14.15 (the minimum for my project) to the latest node version, but none of them really solves the problem.
Some issues were, or are opened on Github about the same problem but all of them are for developing at local machines. The accepted solution is mostly rm -rf node_modules *-lock.json and reinstall the node dependencies but I don’t think I have that in Netlify environment.
Thanks for reaching out, and welcome to the Netlify Forums! Can you please share a link to your site as well as the full deploy log from your most recent build? This will help us look into this further.
Since you changed node versions, can you try rebuilding the site after clearing the cache. This can be achieved by selecting the following option Clear cache and deploy site from the Trigger deploy pane on the Deploy page. This can be found on the opposite side of the Search Deploys field.
I tried that as well. Nothing changed. I even deleted the repository on Netlify and redid the whole site setting again but it seems to me there is an internal error with Netlify.
I has been using Netlify and the same configuration since I first started this project and somehow one day, it doesn’t work anymore.
I have also imported my repository to other clouds like Vercel and Gatsby Cloud. Both of them works just fine to me.
Thanks for reaching out. As you have redone the site, I cannot see anything when I follow the link to your failed deployed.
I have taken a look at some of your deploy logs on your account though, and it looks like one of your sites is using an outdated gatsby plugin. (Looking here)-- can you update your gatsby plugin as well as the node version that is supported, and try deploying again?
Thank you for your time. I totally forgot that you couldn’t view the log when I redid the site.
Depsite your suggestion, none of them really fixed the problem. Here’s the latest log from the current project:
The ones you mentioned are old and I’m no longer working on them.
Unfortunately, I need to see my app in production after I finish a feature. But this bug has been preventing me from doing for like 5 days. I have to migrate to another cloud platform to continue the project.
If you need any more information, please let me know and I’ll see what I can do.
I’m not sure the link keeps getting not found error. Here is the latest build log from my project. I have created a new site for the purpose of troubleshooting this issue.
I have used Netlify for a long time and I have to migrate to another platform reluctantly. So I would love to help your team figure out what’s happening.
We deployed a fresh cone of the repo and using only the flag --legacy-peer-deps we were able to successfully deploy. Could you try deploying while only using --legacy-peer-deps and see if you’re still having issues?
