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
Firstly, thanks so much for making this awesome tool! This may not be something in your power to address, but I thought I'd create a ticket since there doesn't yet seem to be one on the topic of version pinning within the ESM CDN.
So for context, I recently discovered that the latest version of ESM (v96) has a regression that breaks support for the graphql module, which I've just now reported here:
I can fix the tests by pinning the version back to v95 (achieved by adding a ?pin=v95 suffix to the ESModule URL) however, but doing this causes my build to fail with the following error:
panicked at 'dnt bug - Could not find mapping for types code specifier https://esm.sh/v95/graphql@16.5.0/error/GraphQLError.d.ts', rs-lib\src\mappings.rs:97:9
Any thoughts / suggestions here would be very much appreciated?
The text was updated successfully, but these errors were encountered:
Hi 馃憢.
Firstly, thanks so much for making this awesome tool! This may not be something in your power to address, but I thought I'd create a ticket since there doesn't yet seem to be one on the topic of version pinning within the ESM CDN.
So for context, I recently discovered that the latest version of ESM (
v96
) has a regression that breaks support for thegraphql
module, which I've just now reported here:I can fix the tests by pinning the version back to
v95
(achieved by adding a?pin=v95
suffix to the ESModule URL) however, but doing this causes my build to fail with the following error:Any thoughts / suggestions here would be very much appreciated?
The text was updated successfully, but these errors were encountered: