Package Exports #863
Replies: 6 comments 21 replies
-
I voted stuck because ESM support in Jest is still experimental. I have not been able to get Jest working with |
Beta Was this translation helpful? Give feedback.
-
This may help users out https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-rc/#respecting-file-extensions-and-packagejson-in-other-module-modes |
Beta Was this translation helpful? Give feedback.
-
I voted stuck because ESM support in react-native is experimental (via |
Beta Was this translation helpful? Give feedback.
-
We are using NestJS with graphql-request in our projects as well and so far I couldn't find any configuration allowing us to migrate to v7.1.0 with minimal changes. Ultimately, the configuration that displays the least errors is
but open compilation, we are getting this error
Now we don't have any errors in the source code, but the dist directory |
Beta Was this translation helpful? Give feedback.
-
I am happy to see this change from TypeScript. I believe this will widen the path of possible configurations that users can use to work with modern JS packages in TS. One thing that I am not sure about at the moment is if this implies that TS will also kick in its |
Beta Was this translation helpful? Give feedback.
-
Working on an Expo application. Not completely stuck, but quite affected by this decision:
|
Beta Was this translation helpful? Give feedback.
-
Newer versions of GraphQL Request require TypeScript to be configured such that it will read
package.exports
. This decision is to help modernize the community, like with some popular library authors over the past few years have switched over to ESM-only packages. It also reduces my burden by preventing unofficial deep imports.This poll does not mean a democratic decision/change is happening, but I am curious about the results.
If you vote for "...stuck..." please leave a comment about why.
Thanks!
Related:
34 votes ·
Beta Was this translation helpful? Give feedback.
All reactions