Open jamescqcampbell opened 1 month ago
i think it's a resoving bug of esm.sh, i will look into it
seems v136 works correctly, but it has not not been deployed yet
@ije thanks so much for the quick response. I know that you're still working on v136 - do you know of a good workaround to use before that comes out?
i will add a fixpatch for v135 tmr
Thank you so much!
I've patched an npm module and would like to use my fork in deno. However, I have an issue where the type declarations generated by esm.sh do not seem to have a matching path as / is omitted for type definitions.
Is there a misconfiguration on my side?
Failing module type import - wrong namespace generated
Module is exported correctly:
i.e.
But type defs are then only exported at:
Which then resolves to the wrong types in deno.
Additional info