Unable to specify Subdirectory once module published

[Tom-Hudson]

I am the author of https://deno.land/x/test_nino

I used the instructions found here to originally setup the module and never set the optional Subdirectory.

Since then I have started using the denoify npm package to create a deno version of my module inside the deno_dist directory: https://deno.land/x/[email protected]/deno_dist

However, I now have no way to update the config and specify the submodule.

Please can you update this for me? And maybe consider a way in the future for others that adopt usage of something like denoify to do this themselves.

[kitsonk]

@Tom-Hudson if you could please e-mail [email protected] and we can provide more direct support to be able to update information in the backend system and coordinate publishing for the module.

[AndresPrez]

@kitsonk do you mind posting more documentation on how subdirectories work? My plan is to publish many deno modules based on different folders in a single github repo

[Tom-Hudson]

@Tom-Hudson if you could please e-mail [email protected] and we can provide more direct support to be able to update information in the backend system and coordinate publishing for the module.

I emailed a month ago and had no reply...

[ssalbdivad]

@Tom-Hudson I ran into the same issue thinking it was some sort of internal config that I'd have to email about, but missed the fact that the "Subdirectory" option actually just adds a query parameter to the request URL that can be modified directly on GitHub, as was mentioned in this issue which links to this API reference.

@kitsonk Obviously, this was a pain to track down and it would be great if there were clearer documentation about publishing and managing modules on deno.land.

[Tom-Hudson]

@ssalbdivad thank you so much. I never did have a reply to my email and this is still a problem I have.

I was actually thinking about dropping deno support through frustration and just letting people import as an npm module.

I'll update the webhook URL and hopefully have this working for the next version. It is annoying since you can't unpublish older versions, but oh well. Feels like this should be mentioned in the denoify docs. I might do a PR if I find a good place to add it.

[ssalbdivad]

@Tom-Hudson I'm on a tight deadline and was considering whether it was worth posting, but it really brightened my day to learn it was helpful, so thanks 🥰

Tagging @lucacasonato since it looks like @kitsonk might not be working on Deno right now. I'm sure it would save some devs a lot of hassle even to just link to the existing API doc from the "Advanced Options" section of https://deno.land/add_module.