-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Next-Axiom Typescript Issues #144
Comments
hi @YourAverageTechBro , looks like we didn't take dynamic segments into account, the problem comes from this type def. For now, I think maybe you can create your own version of the |
I have a different type issue I use NextRequest
I get the following error
I'm reading the code in the repo and I don't find Request but in the npm package I have I see AxiomRequest defined as
any idea why is taht I checked and I'm on |
|
Hey, we're looking into this right now, thanks for reporting! |
I am getting an error with the following NextJS 13 Route Handler endpoint.
The file path for this is
chatConversation/[chatConversationId]/route.ts
, so the error seems to be the fact that I am trying to access the params in the dynamic route segment in NextJS.When deploying this to Vercel, I get the following error:
The POST function seems to return a NextConfig when passing in the params whereas in my other routes that do not have dynamic route segments it returns a NextHandler.
How do I fix this?
The text was updated successfully, but these errors were encountered: