TypeScript clarification

Tl;DR: Can’t get the autoPrefix thing to work with TS files & ts-node.

I’ve tried to use autoPrefix two ways with TypeScript files, and I cannot seem to find a way to it to work as expected.

Things I’ve tried

First Attempt

I tried to add the options.prefix to the Autoload call, like so

// server.ts
import * as Fastify from 'fastify';
import * as Autload from 'autoload';
import { join } from 'path';

const fastify = Fastify();
fastify.register(Autoload, {
  dir: join(process.cwd(), 'services'),
  includeTypeScript: true,
  options: {
    prefix: '/api'
  }
}

fastify.listen(3000, '0.0.0.0', (err, address)=> {
  if(err) {
    console.error(err);
    process.exit();
  }
  console.log(`Listening on ${address}`);
})

// services/user.ts
module.exports = (fastify, opts, next)=>{
  fastify.get('/user', (req, reply)=> { reply.send('hi'); });
  next();
}

This only adds in the /user route, and not /api/user

Second Attempt

Basically the same server.ts setup, minus the options object.

// services/user.ts
module.exports = (fastify, opts, next) => {
  fastify.get('/user', (r, reply)=>{reply.send('hi'); })
  next();
}

module.exports.autoPrefix = '/api';

In both cases /api/user is not found, but /user is.

Any tips on how to fix this? I’d be happy to submit a pull request for the documentation once I have a solution.

[jhechtf]

Alright, I’ll look into what can be done to resolve the issue – might take me a bit since I’m swamped with my 9-5 right now, and I’m going to have to look into fastify-plugin to determine what’s going on from that end.

[diego-betto]

@jhechtf it’s not a bug, it’s how fastify works. It’s documented in https://www.fastify.io/docs/latest/Plugins/#route-prefixing-option.

Now we get 404 there