no such file or directory, open - gatsby-plugin-s3/src/gatsby-node.ts
See original GitHub issueWhen I’m running gatsby build
, this is what I see on the console
ERROR
UNHANDLED REJECTION ENOENT: no such file or directory, open '/node_modules/gatsby-plugin-s3/src/gatsby-node.ts'
I tried these steps but none of them seem to work
- Did
gatsby clean
- Removed
node_modules
and re installed - Did
gatsby build
Issue Analytics
- State:
- Created 3 years ago
- Comments:8
Top Results From Across the Web
ENOENT: no such file or directory in Gatsby - Stack Overflow
So every time I need to run a gatsby develop I run yarn start or npm run start instead, executing the gatsby clean...
Read more >Troubleshooting Common Errors - Gatsby
comes up when a GraphQL query is trying to query a field for subfields, but none exist. This generally happens when plugins that...
Read more >gatsby-plugin-mdx - npm
Make sure that any gatsby-remark-* plugins are only listed inside the gatsbyRemarkPlugins array of gatsby-plugin-mdx , not inside the plugins ...
Read more >Gatsby Changelog | 5.3.0
Please note: The TypeScript variants of gatsby-config and gatsby-node do not support ESM yet. We plan on adding support in a future minor...
Read more >How To Use Static Files in Gatsby | DigitalOcean
Like many popular Static Site Generators, Gatsby embraces the use of dynamic web frameworks, using React on the frontend and Node.js on the ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi , i had this issue before , and the reason is having more than 50 redirect url without adding this flag generateRedirectObjectsForPermanentRedirects
I think I found the issue. I was creating ~20k redirects without having the flag
generateRedirectObjectsForPermanentRedirects
set to true, that fixed my issue