fix: routes

[simoncarbajal]

This fixes the following issue:

Checklist

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[mcollina]

@jdhollander can you take a look at this? I have a feeling this might undo some of your work.

[jdhollander]

@simoncarbajal Can you give me some more context on where you're getting this? I think the issue is one of not using a leading slash on your prefix?

I don't think reverting the relative routes as in this PR is a good idea, because then we break the fix made for the reverse proxy usage. (#164)

I can certainly see a case to be made that a leading slash should be checked for and included if absent in this location. Also, I spot that I missed line 19 of index-html.js, so that needs fixing too.

When I have a moment, I'll make a PR for it, or would you @simoncarbajal like to amend your PR to check for the slash and add it if missing?

[simoncarbajal]

@jdhollander I just checked and adding a leading slash fixes the issue, thanks!
Checking for the leading slash and adding it if it's missing would be a nice time saver for the rest of us :)

[jdhollander]

@simoncarbajal Glad you're working ok.

I can't see anything in the fastify docs that suggests a prefix without a leading slash is valid - all the examples have a leading slash. Therefore, I'm now not sure it's worth the effort to check for the slash.