Swagger 1.1.0 does NOT load anymore #133

cholasimmons · 2024-07-21T11:25:12Z

I recently updated Elysia to 1.1.3 and Swagger to 1.1.0,
Off the bat helmet() prevented Elysia from running, which was fixed by rolling Elysia back to v1.1.2.
Then I noticed Swagger doesn't load at all (in either versions of Elysia), but rolling it back to version v1.0.5 worked instantly

marclave · 2024-07-21T20:09:09Z

hi @cholasimmons whats the error youre seeing? im just looking into this now : )

cholasimmons · 2024-07-21T21:07:15Z

There's no error at all, the browser screen is actually just throwing a response that it would normally throw when the route exists (but you're not permitted to view it), it's almost like swagger is not loading at all.
The minute I downgrade to 1.0.5 it works instantly.

The recent Elysia update 1.1.3 gave me some issues with helmet() so maybe the problem is coming from there? In the past I recall helmet used to prevent swagger from loading without a little "directives" patch.

If it helps @marclave , here's the repo I was using: cholasimmons/bun-elysia-modular_auth

anthony-legalfly · 2024-07-24T14:16:17Z

Can confirm, this doesn't work on Swagger 1.1.0, downgraded to 1.0.5 and worked out of the box again.

The /health checks works without a bearer token and the authenticated routes I have after these as well. The Swagger endpoints seems to get routed through the authentication because I get the Unauthorized error.

const app = new Elysia()
    .use(
        swagger( {
            documentation: {
                info: {
                    title: 'LegalFly\'s On Prem Server Documentation',
                    version: '1.0.0',
                },
            },
        } ),
    )
    .decorate( "healthController", new HealthController() )
    .get( "/health",
        async ( { healthController } ) => await healthController.checkHealth() )
    .use( bearer() )
    .derive( async ( { bearer } ) =>
    {
        if ( !bearer || bearer !== appConfig.secret ) {
            throw new Error( "Unauthorized" );
        }
    } )

0xd8d · 2024-08-06T05:22:46Z

Can confirm, this doesn't work on Swagger 1.1.0, downgraded to 1.0.5 and worked out of the box again.

The /health checks works without a bearer token and the authenticated routes I have after these as well. The Swagger endpoints seems to get routed through the authentication because I get the Unauthorized error.
const app = new Elysia()
    .use(
        swagger( {
            documentation: {
                info: {
                    title: 'LegalFly\'s On Prem Server Documentation',
                    version: '1.0.0',
                },
            },
        } ),
    )
    .decorate( "healthController", new HealthController() )
    .get( "/health",
        async ( { healthController } ) => await healthController.checkHealth() )
    .use( bearer() )
    .derive( async ( { bearer } ) =>
    {
        if ( !bearer || bearer !== appConfig.secret ) {
            throw new Error( "Unauthorized" );
        }
    } )

Same here. Any solution?

marclave · 2024-08-06T15:19:09Z

investigating today!

immediately im not sure whats up 🤔

lomithrani · 2024-08-19T13:56:56Z

I have an error on 1.1.0+ when starting my app , rolled back successfully to 1.05. I think this is probably related
Error when starting is : (plugin2 is swagger)

6793 |           if (plugin2 instanceof _Elysia) return this._use(plugin2);
6794 |           if (typeof plugin2.default === "function")
6795 |             return plugin2.default(this);
6796 |           if (plugin2.default instanceof _Elysia)
6797 |             return this._use(plugin2.default);
6798 |           throw new Error(
                       ^
error: Invalid plugin type. Expected Elysia instance, function, or module with "default" as Elysia instance or function that returns Elysia instance.
      at [...]/node_modules/elysia/dist/cjs/index.js:6798:17

assapir · 2024-08-27T13:57:36Z

Same problem here.

3218 |                                                  return plugin.default(this)
3219 | 
3220 |                                          if (plugin.default instanceof Elysia)
3221 |                                                  return this._use(plugin.default)
3222 | 
3223 |                                          throw new Error(
                   ^
error: Invalid plugin type. Expected Elysia instance, function, or module with "default" as Elysia instance or function that returns Elysia instance.
      at /Users/assaf/code/work/sidedish/apps/api/node_modules/elysia/src/index.ts:3223:13

when using Swagger, the error disappears when commented out.

in package.json: "@elysiajs/swagger": "^1.0.5",
in lock file:

"@elysiajs/swagger@^1.0.5": 
  version "1.1.1"
  resolved "https://registry.npmjs.org/@elysiajs/swagger/-/swagger-1.1.1.tgz"
  integrity sha512-fsg5IZaNbgN2kWqSRUntSMqg386cmFbT7IrYm2gH1P9e34ZD2wuKhRCu521+T924UunwIHP2+tj6CoFL4FrsxQ==
  dependencies: 
    lodash.clonedeep "^4.5.0"
    openapi-types "^12.1.3

Confirmed to work when pinning the version to 1.0.5

tanishqmanuja · 2024-08-30T05:01:54Z

Same here, 404 NOT_FOUND

Edit:
It was a malfunctioning middleware called after swagger.

For anyone else facing this issue .. try to move the swagger plugin to the topmost level and see if it works.

cham11ng · 2024-09-02T18:26:12Z

For anyone else facing this issue .. try to move the swagger plugin to the topmost level and see if it works.

Tried moving it, still the same. I am facing same issue as @DaniumX - #133 (comment).

 "@elysiajs/jwt": "^1.1.0",
 "@elysiajs/swagger": "^1.1.1",
 "elysia": "^1.1.8",

0xd8d · 2024-09-08T13:04:09Z

Another problem is that Swagger breaks completely if you use .model().

linmeii · 2024-09-17T21:35:50Z

Can confirm, swagger is breaking while using .model()

When entering /swagger page im getting error on /swagger/json that can't find some model in my codebase.
It prevents to generate any routes with tags

codecorsair · 2024-09-20T05:11:19Z

I get the same issue with the "Invalid plugin type." error with version 1.1.1 of @elisiajs/swagger within a SvelteKit server page. Changing @elisiajs/swagger to version 1.0.5 does resolve the error within SvelteKit.

ViliamKopecky · 2024-10-09T09:16:46Z

Still not working with @elysiajs/swagger 1.1.5

josemartinez111 · 2024-11-28T10:49:40Z

Same here.
My error:

GET http://localhost:5050/swagger/json 404 (Not Found)
hu @ standalone.js:2996
(anonymous) @ standalone.js:12634
(anonymous) @ standalone.js:12654
ar @ standalone.js:639
or @ standalone.js:640
(anonymous) @ standalone.js:1157
y @ standalone.js:622
(anonymous) @ standalone.js:627
Ao @ standalone.js:1160
Co @ standalone.js:1152
GD @ standalone.js:12653
setup @ standalone.js:26832
ar @ standalone.js:639
(anonymous) @ standalone.js:1031
(anonymous) @ standalone.js:1028
T @ standalone.js:1023
E @ standalone.js:1009
f @ standalone.js:960
s @ standalone.js:1060
run @ standalone.js:411
A @ standalone.js:1065
T @ standalone.js:1035
E @ standalone.js:1009
f @ standalone.js:960
z @ standalone.js:1137
mount @ standalone.js:905
(anonymous) @ standalone.js:1480
o @ standalone.js:26867
(anonymous) @ standalone.js:26868
(anonymous) @ standalone.js:16
(anonymous) @ standalone.js:16Understand this errorAI
standalone.js:2997 [fetchSpecFromUrl] Failed to fetch the specification at /swagger/json (Status: 404)
hu @ standalone.js:2997
await in hu
(anonymous) @ standalone.js:12634
(anonymous) @ standalone.js:12654
ar @ standalone.js:639
or @ standalone.js:640
(anonymous) @ standalone.js:1157
y @ standalone.js:622
(anonymous) @ standalone.js:627
Ao @ standalone.js:1160
Co @ standalone.js:1152
GD @ standalone.js:12653
setup @ standalone.js:26832
ar @ standalone.js:639
(anonymous) @ standalone.js:1031
(anonymous) @ standalone.js:1028
T @ standalone.js:1023
E @ standalone.js:1009
f @ standalone.js:960
s @ standalone.js:1060
run @ standalone.js:411
A @ standalone.js:1065
T @ standalone.js:1035
E @ standalone.js:1009
f @ standalone.js:960
z @ standalone.js:1137
mount @ standalone.js:905
(anonymous) @ standalone.js:1480
o @ standalone.js:26867
(anonymous) @ standalone.js:26868
(anonymous) @ standalone.js:16
(anonymous) @ standalone.js:16Understand this errorAI
standalone.js:2998 [fetchSpecFromUrl] Tried to fetch the specification (url: /swagger/json) without a proxy. Are the CORS headers configured to allow cross-domain requests? https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS
hu @ standalone.js:2998
await in hu
(anonymous) @ standalone.js:12634
(anonymous) @ standalone.js:12654
ar @ standalone.js:639
or @ standalone.js:640
(anonymous) @ standalone.js:1157
y @ standalone.js:622
(anonymous) @ standalone.js:627
Ao @ standalone.js:1160
Co @ standalone.js:1152
GD @ standalone.js:12653
setup @ standalone.js:26832
ar @ standalone.js:639
(anonymous) @ standalone.js:1031
(anonymous) @ standalone.js:1028
T @ standalone.js:1023
E @ standalone.js:1009
f @ standalone.js:960
s @ standalone.js:1060
run @ standalone.js:411
A @ standalone.js:1065
T @ standalone.js:1035
E @ standalone.js:1009
f @ standalone.js:960
z @ standalone.js:1137
mount @ standalone.js:905
(anonymous) @ standalone.js:1480
o @ standalone.js:26867
(anonymous) @ standalone.js:26868
(anonymous) @ standalone.js:16
(anonymous) @ standalone.js:16Understand this warningAI
standalone.js:12637 Failed to fetch spec from URL: Error: Failed to fetch the specification (Status: 404)
    at hu (standalone.js:2999:1)
    at async standalone.js:12634:17
    at async standalone.js:12654:28
(anonymous) @ standalone.js:12637
await in (anonymous)
(anonymous) @ standalone.js:12654
ar @ standalone.js:639
or @ standalone.js:640
(anonymous) @ standalone.js:1157
y @ standalone.js:622
(anonymous) @ standalone.js:627
Ao @ standalone.js:1160
Co @ standalone.js:1152
GD @ standalone.js:12653
setup @ standalone.js:26832
ar @ standalone.js:639
(anonymous) @ standalone.js:1031
(anonymous) @ standalone.js:1028
T @ standalone.js:1023
E @ standalone.js:1009
f @ standalone.js:960
s @ standalone.js:1060
run @ standalone.js:411
A @ standalone.js:1065
T @ standalone.js:1035
E @ standalone.js:1009
f @ standalone.js:960
z @ standalone.js:1137
mount @ standalone.js:905
(anonymous) @ standalone.js:1480
o @ standalone.js:26867
(anonymous) @ standalone.js:26868
(anonymous) @ standalone.js:16
(anonymous) @ standalone.js:16Understand this errorAI
standalone.js:2996 
        
        
       GET http://localhost:5050/swagger/json 404 (Not Found)
hu @ standalone.js:2996
importSpecFromUrl @ standalone.js:17950
(anonymous) @ standalone.js:18172
init @ standalone.js:18168
(anonymous) @ standalone.js:18178
(anonymous) @ standalone.js:786
ar @ standalone.js:639
or @ standalone.js:640
(anonymous) @ standalone.js:784
br @ standalone.js:661
z @ standalone.js:1138
mount @ standalone.js:905
(anonymous) @ standalone.js:1480
o @ standalone.js:26867
(anonymous) @ standalone.js:26868
(anonymous) @ standalone.js:16
(anonymous) @ standalone.js:16Understand this errorAI
standalone.js:2997 [fetchSpecFromUrl] Failed to fetch the specification at /swagger/json (Status: 404)
hu @ standalone.js:2997
await in hu
importSpecFromUrl @ standalone.js:17950
(anonymous) @ standalone.js:18172
init @ standalone.js:18168
(anonymous) @ standalone.js:18178
(anonymous) @ standalone.js:786
ar @ standalone.js:639
or @ standalone.js:640
(anonymous) @ standalone.js:784
br @ standalone.js:661
z @ standalone.js:1138
mount @ standalone.js:905
(anonymous) @ standalone.js:1480
o @ standalone.js:26867
(anonymous) @ standalone.js:26868
(anonymous) @ standalone.js:16
(anonymous) @ standalone.js:16Understand this errorAI
standalone.js:2998 [fetchSpecFromUrl] Tried to fetch the specification (url: /swagger/json) without a proxy. Are the CORS headers configured to allow cross-domain requests? https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS
hu @ standalone.js:2998
await in hu
importSpecFromUrl @ standalone.js:17950
(anonymous) @ standalone.js:18172
init @ standalone.js:18168
(anonymous) @ standalone.js:18178
(anonymous) @ standalone.js:786
ar @ standalone.js:639
or @ standalone.js:640
(anonymous) @ standalone.js:784
br @ standalone.js:661
z @ standalone.js:1138
mount @ standalone.js:905
(anonymous) @ standalone.js:1480
o @ standalone.js:26867
(anonymous) @ standalone.js:26868
(anonymous) @ standalone.js:16
(anonymous) @ standalone.js:16Understand this warningAI
standalone.js:17951 Failed to fetch spec from URL: Error: Failed to fetch the specification (Status: 404)
    at hu (standalone.js:2999:1)
    at async importSpecFromUrl (standalone.js:17950:7)
    at async standalone.js:18172:29
    at async init (standalone.js:18168:7)
    at async standalone.js:18178:29
importSpecFromUrl @ standalone.js:17951
await in importSpecFromUrl
(anonymous) @ standalone.js:18172
init @ standalone.js:18168
(anonymous) @ standalone.js:18178
(anonymous) @ standalone.js:786
ar @ standalone.js:639
or @ standalone.js:640
(anonymous) @ standalone.js:784
br @ standalone.js:661
z @ standalone.js:1138
mount @ standalone.js:905
(anonymous) @ standalone.js:1480
o @ standalone.js:26867
(anonymous) @ standalone.js:26868
(anonymous) @ standalone.js:16
(anonymous) @ standalone.js:16Understand this errorAI
standalone.js:17818 Error: Failed to fetch the specification (Status: 404)
    at hu (standalone.js:2999:1)
    at async importSpecFromUrl (standalone.js:17950:7)
    at async standalone.js:18172:29
    at async init (standalone.js:18168:7)
    at async standalone.js:18178:29

cholasimmons · 2025-01-05T15:53:24Z

I'm now on Elysia 1.2.9, Swagger 1.2.0 still isn't doing what it's meant to.
So I'm still using 1.0.5, even after trying this helmet fix, or this scalarVersion fix.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Swagger 1.1.0 does NOT load anymore #133

Swagger 1.1.0 does NOT load anymore #133

cholasimmons commented Jul 21, 2024

marclave commented Jul 21, 2024

cholasimmons commented Jul 21, 2024 •

edited

Loading

anthony-legalfly commented Jul 24, 2024

0xd8d commented Aug 6, 2024

marclave commented Aug 6, 2024 •

edited

Loading

lomithrani commented Aug 19, 2024

assapir commented Aug 27, 2024 •

edited

Loading

tanishqmanuja commented Aug 30, 2024 •

edited

Loading

cham11ng commented Sep 2, 2024

0xd8d commented Sep 8, 2024

linmeii commented Sep 17, 2024 •

edited

Loading

codecorsair commented Sep 20, 2024

ViliamKopecky commented Oct 9, 2024

josemartinez111 commented Nov 28, 2024 •

edited

Loading

cholasimmons commented Jan 5, 2025

Swagger 1.1.0 does NOT load anymore #133

Swagger 1.1.0 does NOT load anymore #133

Comments

cholasimmons commented Jul 21, 2024

marclave commented Jul 21, 2024

cholasimmons commented Jul 21, 2024 • edited Loading

anthony-legalfly commented Jul 24, 2024

0xd8d commented Aug 6, 2024

marclave commented Aug 6, 2024 • edited Loading

lomithrani commented Aug 19, 2024

assapir commented Aug 27, 2024 • edited Loading

tanishqmanuja commented Aug 30, 2024 • edited Loading

cham11ng commented Sep 2, 2024

0xd8d commented Sep 8, 2024

linmeii commented Sep 17, 2024 • edited Loading

codecorsair commented Sep 20, 2024

ViliamKopecky commented Oct 9, 2024

josemartinez111 commented Nov 28, 2024 • edited Loading

cholasimmons commented Jan 5, 2025

cholasimmons commented Jul 21, 2024 •

edited

Loading

marclave commented Aug 6, 2024 •

edited

Loading

assapir commented Aug 27, 2024 •

edited

Loading

tanishqmanuja commented Aug 30, 2024 •

edited

Loading

linmeii commented Sep 17, 2024 •

edited

Loading

josemartinez111 commented Nov 28, 2024 •

edited

Loading