server lifecycle timing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
https://github.com/nuxt/nuxt.js/issues/11428
@danielroe we have server timings for loading chunks but would be nice to know (particularly where we are performing internal $fetch) what the timings for each handler are
Context and how-to are not really clear to me at the moment but we might benefit from more nitro lifecycle hooks to make such a thing possible.
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 by reading the linked Nuxt issue and the related hookable issue; the payload names no Nitro files, tests, or entry points. Clarify which server lifecycle and handler timings are required, then identify the Nitro hook surface involved; done should be an agreed scope with corresponding tests and usage guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100