Next.js 13 Web Vitals & React Server Components #120
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
I've created a webvitals component (not tested yet). |
|
|
||
| Bugs, feature requests, and development-related questions should be directed to our GitHub [issue tracker.](https://github.com/axiomhq/next-axiom/issues) | ||
|
|
||
| When reporting a bug, please try and provide as much context as possible such as your operating system, NodeJS version and anything else that might be relevant to the bug. For feature requests, please explain what you're trying to do and how the requested feature would help you do that. |
There was a problem hiding this comment.
Can we ask/encourage minimal repro's for bugs alongside the info?
| @@ -48,7 +48,7 @@ | |||
| "ts-jest": "~29.1", | |||
| "ts-node": "^10.8.0", | |||
| "turbo": "^1.9.9", | |||
| "typescript": "^4.6.4" | |||
There was a problem hiding this comment.
ahhh, all the sweeeeeet wins
this avoids a whole host of issues with next-13, see: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-5-1.html#decoupled-type-checking-between-jsx-elements-and-jsx-tag-types, don't know if we hit them or not but good to know
This is what the user will see when they update their next12 project to use next-axiom v0.19.0, It's not helpful though. using pnpm, I was not able to see any peer deps warnings. |
|
do we still need to send edge reports or does vercel now send reports for all types of routes? |
|
Closing for #134 |
how can i resolve this? seeing it atm |
|
@niklasp There is not next-axiom v0.19, the next version is v1.0 and that requires Next.js 13. |
This drops support for Next.js 12 and adds two hooks:
useLoggerwhich returns an Axiom loggeruseReportWebVitalswhich reports web vitals automatically