Package Exports

[jasonkuhrt]

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.

• https://www.typescriptlang.org/docs/handbook/modules/reference.html#node16-nodenext-1
• https://www.typescriptlang.org/docs/handbook/modules/reference.html#bundler

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:

• Document the requirement of tooling support for package.exports #845

[mrbfrank]

I voted stuck because ESM support in Jest is still experimental. I have not been able to get Jest working with moduleResolution:bundler yet, still working on it. My team is evaluating replacing Apollo with react-query + graphql-request, but the latest ESM-only requirement is causing some friction.

[jasonkuhrt]

Thanks for sharing @mrbfrank. Jest has been an issue for years, been there myself :(

The sense I get is developers are migrating to Playwright, Vitest, or Node's native test runner more and more.

[jonkoops]

Have you tried switching to Vitest for testing? It is largely API compatible with Jest and supports ESM out of the box.