Bypass VPS on selected routes

[brillout]

Moved from #568 (comment) @TomLadek:

@bagr001 What's your motivation for not completely bypassing VPS and creating a normal Fastify route instead?

@brillout What would be the standard way to bypass VPS on selected routes? I have a very similar situation as bagr001 in that I want to use VPS client routing for most routes as well as some API GET routes handled (exclusively) by the server.

My current solution is to create a dummy route in pages/ but I feel there has to be a nicer way:

// pages/rest/rest.page.route.js
export default "/rest/*"

// pages/rest/_default.page.server.js
export async function render() {
  return {}
}

// server/index.js
app.get('/rest/*', (req) => {
  ...
})

[brillout]

@TomLadek Have you seen https://vite-plugin-ssr.com/api-routes?

[TomLadek]

@brillout Thanks! But adding a new dependency like Telefunc or tRPC seems like an overkill for me right now. I'll stick with the solution with the dummy route for the moment.

[samuelstroschein]

If you use VPS with a middleware, place the VPS middleware last to bypass the catch-all routes.

See https://github.com/inlang/inlang/blob/f491813bdfea8856d261b6bcd8525506f153f68c/source-code/server/src/main.ts#L53. We have one server that deploys RPCs, APIs, reverse proxies and vite plugin ssr. Works fabulous!

[TomLadek]

You're right, it's just the ordering of the routes 🤦🏻I've moved the VPS catch-all-route after the /rest route declarations and now I don't need the dummy files in pages/rest/. Thanks!

[brillout]

I updated the docs 4bef983 https://vite-plugin-ssr.com/api-routes

(@TomLadek In case you think you can convince your employer: https://github.com/sponsors/brillout. Sponsors are starting to have a tremendous impact.)