contentlayerdev / contentlayerdev/website
Deleting cache directory as a troubleshooting effort
Open
documentation
- Dominant language
- TypeScript
- Stars
- 132
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
Might be worth mentioning somewhere that one possible way to debug is to delete the `.contentlayer` directory and restart the server. But ideally users would also log issues along the way.
Contributor guide
No contributing guide indexed for this repository
Research direction
No documentation file or test is named. Start by locating the website's troubleshooting guidance, then add the note about deleting `.contentlayer` and restarting the server, along with the suggestion to log issues encountered. Done means users can find this troubleshooting step in the documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100