[POC] of next13 support on top of @axiomhq/js

[dasfmi]

This is a POC of next13 logging and webivtals support on top of @axiomhq/js. This would help us better understand the requirements for the JS sdk and the challenges in supporting other layers on top.

Challenges / TODOs / Questions:

• enforce error/warn if dataset name or token not resolved successfully.
• catch client errors to stop breaking api functions or pages
• test flushing
• give the user the option to disable client batching
• How to support client components without exposing axiom token?
• do we handle the usage of navigator.becon in axiom/js?
• how to handle the url for web-vitals? vercel integration has a special webVital endpoint

what would be the user-agent name? next-axiom/v or axiomjs-nextjs/v? or @axiomhq/nextjs/v

[vercel]

@schehata is attempting to deploy a commit to the AxiomFM Team on Vercel.

To accomplish this, @schehata needs to request access to the Team.

Afterwards, an owner of the Team is required to accept their membership request.

If you're already a member of the respective Vercel Team, make sure that your Personal Vercel Account is connected to your GitHub account.