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'm currently trying to use this library inside an angular library. When building the library the locale import will interpreted in a way that I receive {default: {…}, __esModule: true} instead of the locale object. This seems to be a common problem as described here: https://esbuild.github.io/content-types/#default-interop
Maybe it would be a good approach to avoid the default exports for the locale files, so this problem does not occur for other users too.
The text was updated successfully, but these errors were encountered:
Agreed. The way that the locale modules are written is really complicating the usage of this library. If they exported something like "localeEn" by default, then it may be easier to use in a dynamic situation?
I'm currently trying to use this library inside an angular library. When building the library the locale import will interpreted in a way that I receive
{default: {…}, __esModule: true}
instead of the locale object. This seems to be a common problem as described here: https://esbuild.github.io/content-types/#default-interopMaybe it would be a good approach to avoid the default exports for the locale files, so this problem does not occur for other users too.
The text was updated successfully, but these errors were encountered: