[BUG] Swagger issue on loading an undefined resource about tsed

[Romakita]

Ho shit missed this issue. I'll try to find a way to fix that ASAP @VictoriqueMoe ;)

[VictoriqueMoe]

It seems to be coming from the validator badge

[Romakita]

Hello @VictoriqueMoe

I finally decided to use the getAbsolutePath from swagger-ui-dist/get-absolute-path.js it seems to works correctly. I was thinking importing file directly (when exports isn't defined in the package.json of the module) doesn't works in ESM. Finally, if exports is missing, ESM can import any files in the package.

It should solve your issue ;)
See you

[github-actions]

🎉 Are you happy?

If you appreciated the support, know that it is free and is carried out on personal time ;)

A support, even a little bit makes a difference for me and continues to bring you answers!

[Romakita]

🎉 This issue has been resolved in version 7.68.6 🎉

The release is available on:

• v7.68.6
• GitHub release

Your semantic-release bot 📦🚀

[VictoriqueMoe]

Hello @VictoriqueMoe

I finally decided to use the getAbsolutePath from swagger-ui-dist/get-absolute-path.js it seems to works correctly. I was thinking importing file directly (when exports isn't defined in the package.json of the module) doesn't works in ESM. Finally, if exports is missing, ESM can import any files in the package.

It should solve your issue ;) See you

@Romakita

unfortantly, this did not solve the issue, i still get these 404's and the validator badge still errors

i deployed the latest tsed and you can see the error here: https://waifuvault.moe/api-docs/

[Romakita]

Ok. But now the path is directly get from swagger-ui-dist. So it's not related to the latest changes. Maybe the problem is related to swagger-ui-dist itself?

[Romakita]

But we can see a undefined string in the url. I'll check if other changes have introduce this regression. It's a bit complicated to repro in local when the badge is only displayed on a non localhost domain. I'll keep you informed if I found something ;)
And sorry for this unresolved issue!

[VictoriqueMoe]

But we can see a undefined string in the url. I'll check if other changes have introduce this regression. It's a bit complicated to repro in local when the badge is only displayed on a non localhost domain. I'll keep you informed if I found something ;) And sorry for this unresolved issue!

yeh, it's annoying for sure that is hard to test. editing the hosts file to proxy a localhost domain worked for me.

also, no problem! it's not really a blocker. However, this is a blocker: https://github.com/orgs/tsedio/discussions/2697 if that counts for anything :D

thank you as always for your amazing support and help