/swagger/json returning 404 if Swagger is used in conjunction with a prefix set in Elysia

[sludgepudge]

When setting a prefix in Elysia and simultaneously using Swagger, it fails to correctly load /swagger/json.

To reproduce:

new Elysia({ prefix: '/v1' })
	.use(swagger())
	.use(logixlysia()) // logger used to highlight responses on console
	.get('/', () => 'Hello!')
	.listen(3000);

Visit the server in a browser http://localhost:3000/v1/swagger and you'll be presented with the UI theme of Scalar, but no content.

Adding a logger reveals that /v1/swagger gets hit and returns a 200 status, immediately followed by /swagger/json (note the lack of prefix) getting hit with a 404 status.

It seems this has been attempted to be fixed before #16 but has remained an ongoing issue since at least October 2024.

[Mikey-ShenSu]

If you’re using Next.js, here’s a temporary solution to address the issue:

// src/app/swagger/json/page.tsx
import { redirect } from "next/navigation";

export default function SwaggerPage() {
  redirect("/api/swagger/json");
}

For a pure Elysia JS project (used as an API only), you can apply the same approach by redirecting the endpoint to /api/swagger/json. The concept remains the same.

[TheGU]

Thie pr #146 force a path to always start at root instead of relative path, so json file not found when we set a preix in elysia.

[chrisllontop]

@TheGU my apologies for that. I’ll fix that asap. Thanks!

[Euraxluo]

Is it really that complicated?

[Euraxluo]

log:GET /sw.js 404 in 63ms

[ortonomy]

Why was this closed @SaltyAom - it's still an issue today... May 26th 2025...

[MikeyZhang75]

Why was this closed @SaltyAom - it's still an issue today... May 26th 2025...

@ortonomy This issue was actually fixed in previous patches, but the latest version (1.3.0) that he pushed broke it again, even resulting in an empty page after reloading. For now, I recommend rolling back to version 1.2.2 (@elysia/swagger) and waiting for a minor fix.

[sludgepudge]

Why was this closed @SaltyAom - it's still an issue today... May 26th 2025...

@ortonomy This issue was actually fixed in previous patches, but the latest version (1.3.0) that he pushed broke it again, even resulting in an empty page after reloading. For now, I recommend rolling back to version 1.2.2 (@elysia/swagger) and waiting for a minor fix.

It was never fixed, at least not as a result of anything in this issue. When it got closed as fixed I immediately tried it and it still failed exactly as it did before, but I was fed up with the maintainers seemingly not understanding the issue and moved on to a different solution that works better for what I needed.

[ortonomy]

Why was this closed @SaltyAom - it's still an issue today... May 26th 2025...

@ortonomy This issue was actually fixed in previous patches, but the latest version (1.3.0) that he pushed broke it again, even resulting in an empty page after reloading. For now, I recommend rolling back to version 1.2.2 (@elysia/swagger) and waiting for a minor fix.

It was never fixed, at least not as a result of anything in this issue. When it got closed as fixed I immediately tried it and it still failed exactly as it did before, but I was fed up with the maintainers seemingly not understanding the issue and moved on to a different solution that works better for what I needed.

What was your alternative out of interest?

[MikeyZhang75]

Why was this closed @SaltyAom - it's still an issue today... May 26th 2025...

@ortonomy This issue was actually fixed in previous patches, but the latest version (1.3.0) that he pushed broke it again, even resulting in an empty page after reloading. For now, I recommend rolling back to version 1.2.2 (@elysia/swagger) and waiting for a minor fix.

It was never fixed, at least not as a result of anything in this issue. When it got closed as fixed I immediately tried it and it still failed exactly as it did before, but I was fed up with the maintainers seemingly not understanding the issue and moved on to a different solution that works better for what I needed.

@sludgepudge I’m quite certain that version 1.2.2 doesn’t have this issue — I’m currently using it without problems. From what I understand, @SaltyAom is primarily maintaining ElysiaJS and its official plugins, largely on their own. Given that this isn’t backed by a major tech company with dedicated teams, a bit more patience might be fair.

[coscura]

as a workaround, you can use .use(swagger({ specPath: "api/swagger" })), in my case /api is the global prefix