SSR Site construct support for base path option

[Ankcorn]

All the SSR frameworks support rendering on a base path like

example.com/docs

• svelte - https://kit.svelte.dev/docs/configuration#paths
• astro - https://docs.astro.build/en/reference/configuration-reference/#base
• next - https://nextjs.org/docs/pages/api-reference/next-config-js/basePath

I can't get this working with sst :(

[jayair]

Hey Thomas, can you post this on #help and we'll take a look at supporting it.

[jplwood]

@jayair Any updates on this? Searching discord just turns up workarounds and callouts that basePath isn't currently supported. We use basePath extensively with multiple apps behind a reverse proxy, so not having having basePath is certainly a hindrance!

[jayair]

I think this is supported for Astro and maybe Next.js. Which one are you looking for?

[jplwood]

Next.js, yeah, we use it in our app's Next config, but when deployed with SST, that basePath isn't used as a prefix in cloudfront (specifically the app looks for static bundles at <basePath>/.next/*, but the cloudfront route has it as .next/*). That was at least one obvious issue I noticed, not sure if there are other places it should apply?

I've got a workaround for now, but certainly would be nice if the next construct used it when defining the CF routing rules!

[jayair]

Let me check on the Next.js one with the team.

[jplwood]

I derped/lied. My workaround doesn't actually solve the issue. Regarding what I said before:

We use basePath extensively with multiple apps behind a reverse proxy

Without base path support, my next app will request all static bundles and such from the root path /. When behind a reverse proxy, the routing rules will have no idea that the / root requests should be routed to my app without putting all requests behind a basePath. Those requests will be sent to the default routing rule.

So this remains a big hindrance.

---

Curiously. I was just poking around again and I found this deprecated NextjsSite construct (as far as I can tell, it's deprecated because the non-deprecated construct uses SsrSite as a base, whereas the deprecated one doesn't?), and found that this deprecated version actually does support basePath. So this seems to be a regression.

[jplwood]

@jayair since I figured out how basePath was previously done, went ahead and opened a suggested PR ☝️ to address at least the Next.js part of this issue.

[eschaefer]

Just wanted to bump this, since using basePath with NextjsSite seems to result in 403 forbidden errors for static assets for me. Just curious if anyone else using basePath experiences this?