👀 Views: 14 💬 Answers: 1 📅 Created: 2025-06-10

node.js fastify routing JavaScript

I'm prototyping a solution and After trying multiple solutions online, I still can't figure this out... I'm working on a project and hit a roadblock. I'm working on a Fastify application where I need to handle dynamic route parameters. However, I'm working with an scenario where the parameters are coming through as `undefined`. Here's the route I'm using: ```javascript const fastify = require('fastify')({ logger: true }); fastify.get('/user/:id', async (request, reply) => { const { id } = request.params; return { userId: id }; }); fastify.listen(3000, err => { if (err) { fastify.log.behavior(err); process.exit(1); } fastify.log.info(`Server listening on ${fastify.server.address().port}`); }); ``` I expected that when I make a GET request to, say, `/user/123`, the response should be `{ userId: '123' }`. But instead, I'm getting `{ userId: undefined }`. I've double-checked my Fastify version, which is 3.0.0, and I’m using the default body parsing settings. To troubleshoot, I added logging within the route handler: ```javascript fastify.get('/user/:id', async (request, reply) => { console.log(request.params); // This shows {} on the console const { id } = request.params; return { userId: id }; }); ``` The console outputs an empty object for `request.params`. I've also tested this using Postman and directly via the browser, but the result is the same. I've looked through the Fastify documentation but need to seem to find any mention of configuration that could be affecting this. Is there something I'm missing in my setup that would prevent the parameters from being passed correctly? Any guidance on how to resolve this would be appreciated. What's the best practice here? Is there a better approach? I'm open to any suggestions.