We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Windows_NT
v16.14.0
3.0.0-27496606.e43ba6e
npm@8.5.2
vite
typescript
privateRuntimeConfig
-
I have a server folder with
server/api/[uid].get.ts
I just return the context.params
export default defineEventHandler( async ( event ) => { console.log(event.context.params) event.res.end(JSON.stringify(event.context.params)) })
This is empty, but if I change it to server/api/[name].get.ts
server/api/[name].get.ts
I see parameter returned. I tried a few different four letter words and they seem to work. One and two letter words work. longer names work.
parameter names with three letters are ignored by the server. Interestingly, the route is still hit, but the parameter isn't available in context.
No response
The text was updated successfully, but these errors were encountered:
fix: escape regex for wild-card route matcher
41e27b4
nuxt/framework#4313
Hi. This issue should be fixed in nitropack@v0.2.8. Please try upgrading using npx nuxi upgrade --force.
nitropack@v0.2.8
npx nuxi upgrade --force
Sorry, something went wrong.
No branches or pull requests
Environment
Windows_NT
v16.14.0
3.0.0-27496606.e43ba6e
npm@8.5.2
vite
typescript
,privateRuntimeConfig
-
-
Reproduction
I have a server folder with
server/api/[uid].get.ts
I just return the context.params
This is empty, but if I change it to
server/api/[name].get.ts
I see parameter returned. I tried a few different four letter words and they seem to work. One and two letter words work. longer names work.
Describe the bug
parameter names with three letters are ignored by the server. Interestingly, the route is still hit, but the parameter isn't available in context.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: