No valid exports main found for @urql/core - ts-node in a Next.js project

Hello,

As promised, here is a minimal reproduction of an issue I am running into when trying to use the latest version of urql in a Next.js project ran by ts-node.

Note: All works as expected if I use next-urql: 0.3.3 and urql: 1.9.1.

Let me know if I can help with figuring this out.

urql version & exchanges: urql: 1.9.7 next-urql: 0.3.7

Default exchanges used

Steps to reproduce

1. Clone this repository: https://github.com/OriginalEXE/urql-import-problem-reproduction
2. Run npm install
3. Run npm run start and wait for the server to start
4. Visit http://localhost:3000

Expected behavior The website should show “Hello world”

Actual behavior An error is thrown:

Error: No valid exports main found for '/Users/ante/Projects/urql-import-problem-reproduction/node_modules/@urql/core'
    at resolveExportsTarget (internal/modules/cjs/loader.js:611:9)
    at applyExports (internal/modules/cjs/loader.js:492:14)
    at resolveExports (internal/modules/cjs/loader.js:541:12)
    at Function.Module._findPath (internal/modules/cjs/loader.js:643:22)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:941:27)
    at Function.Module._load (internal/modules/cjs/loader.js:847:27)
    at Module.require (internal/modules/cjs/loader.js:1016:19)
    at require (internal/modules/cjs/helpers.js:69:18)
    at Object.<anonymous> (/Users/ante/Projects/urql-import-problem-reproduction/node_modules/urql/dist/urql.js:1:12)
    at Module._compile (internal/modules/cjs/loader.js:1121:30)
    at Module._extensions..js (internal/modules/cjs/loader.js:1160:10)
    at Object.require.extensions.<computed> [as .js] (/Users/ante/Projects/urql-import-problem-reproduction/node_modules/ts-node/src/index.ts:832:44)
    at Module.load (internal/modules/cjs/loader.js:976:32)
    at Function.Module._load (internal/modules/cjs/loader.js:884:14)
    at Module.require (internal/modules/cjs/loader.js:1016:19)
    at require (internal/modules/cjs/helpers.js:69:18) {
  code: 'MODULE_NOT_FOUND'
}

[OriginalEXE]

Woohoo, once I switched to Node 14.0.0, it all works. Thanks so much for making me try this 🎉

I was on 13.2.0 and I can still reproduce this once I switch back to that version, so maybe something specific to that version triggers this issue.

In any case, thanks again for all of your work here, and hopefully, if anyone else out there runs into this issue, this thread helps them as well 😄

[kinday]

We switched back to 12.16.2 and it works. Didn’t work on 13.6.0 though.