Show crawler path traces for error logs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
@Atinux Also to help debug pre-rendering, could we have a way to have more logs about where the links are found? Example:
This is very useful when we hit some 404 and now the process exit
Or shall we simply keep track of where we extracted the route and display where it comes from when displaying the errors leading to an exited process?
I think we might keep a dependency graph for link relations and finally use to generate a trace in error logs like this:
| /api/_content/contributors (82ms) (Error 404)
> Crawled from: "/landing" and "/contributors"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Nitro’s pre-render crawler and the error-reporting path for 404s. Trace how links are discovered and how crawler errors currently exit the process. Done means error logs show the failing route and the route or routes from which it was crawled, with coverage for the reported example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100