Error with newly published module when accessing on Deno website

[chrome lily]

Hi there, I published a module yesterday and when I try to access it, the page only returns: "An error occurred during route handling or page rendering."
https://deno.land/x/pdf_to_jpg@v0.9.1
The module is accessible if you were to go to one of the files within it, though: https://deno.land/x/pdf_to_jpg@v0.9.1/pdfImageConverter.ts
I'm not sure if I've setup something incorrectly or if this a problem on the hosting end, although it seems that I may potentially not be the only one with this issue: https://github.com/denoland/website_feedback/issues/40 (the issue is a little ambiguous though)

[eager scroll]

you are not pulling the actual file you want to use, that's why you are getting the error

oh no wait a minute, it seems like just the rendering page is wrong, my bad

oh, is it because your index isn't exporting anything?

https://deno.land/x/pdf_to_jpg@v0.9.1/index.ts

yeah, that seems to be the case. the page you link doesn't seem to be able to find an appropriate starting point for your module

https://github.com/OM-MediaWorks/PDF-image-converter/blob/main/index.ts
this doesn't have any exports. Your module (i assume) works, but can't be used as a module

[zealous rain]

This does seem to be a bug with the website: You have both 0.9.1 and v0.9.1 published. The website redirects to v0.9.1 and then somehow fails the rendering. Accessing 0.9.1 manually does work.

[signal token]

doesnt have to do with that; the website doesnt care if there is something exported or not

[eager scroll]

would you know what is causing it then?

[signal token]

I am looking into it.

[eager scroll]

alright, sounds good, thanks

[signal token]

I dont see a 0.9.1 tag and dont get that weird behaviour you are encountering

[eager scroll]

do you not see this on the v link?

[signal token]

yes.

[eager scroll]

the non v link says the version does not exist too, so weird

[signal token]

0.9.1 was never published, so not sure why a non-v tag is even mentioned here

[eager scroll]

removing the semver from the link also makes it show this page, but on v1.0.1

is this just a problem with not redirecting to the starting point file?

redirects fine for my module as well, with and without semver on the link https://deno.land/x/prizewinner

feel free to ping me if you want to test a theory, crowl. i'm gonna tune in the #1060609604234510427

[signal token]

no

the reason is the content in the readme

the markdown renderer is trying to handle this link

but errors out

it shouldnt be erroring out thoguh, it just silently ignore the error