[docs-infra] Investigate the report of web vitals
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Just noticed this warning while working on _app.js:
⚠ Fast Refresh had to perform a full reload when ./pages/_app.js changed. Read more: https://nextjs.org/docs/messages/fast-refresh-reload
Looks like it's caused by the reportWebVitals function that is exported. Is this a deprecated next.js feature? I can't find anything about it anymore in the docs, except for these old ones. The current docs seem to mention a useReportWebVitals hook instead.
Actions/ questions to answer
- What does the code is currently reporting?
- Do we need those information or can we rely on Search console for that aspect
- Either update to the up to date way of handling web vital with NextJS, or just drop it
Search keywords:
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 in docs/pages/_app.js at the exported reportWebVitals function and compare its behavior with the current Next.js useReportWebVitals documentation. Determine what data is currently reported and whether Search Console covers it; done means either updating the docs site to the current approach or removing the reporting code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, next.js
- Domain
- documentation, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100