You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
The text was updated successfully, but these errors were encountered: