Error "The package may have incorrect main/module/exports specified in its package.json."

[joulev]

I tried to upgrade my app to use v3.1.2, but without any other code changes, the following error shows up on build:

Error: Failed to resolve entry for package @graphql-typed-document-node/core. The package may have incorrect main/module/exports specified in its package.json.

Call stack

    at packageEntryFailure (file:///Users/joulev/dev/www/webapps/node_modules/.pnpm/vite@4.1.4_@types+node@18.14.1/node_modules/vite/dist/node/chunks/dep-ca21228b.js:22005:11)
    at resolvePackageEntry (file:///Users/joulev/dev/www/webapps/node_modules/.pnpm/vite@4.1.4_@types+node@18.14.1/node_modules/vite/dist/node/chunks/dep-ca21228b.js:22002:5)
    at tryNodeResolve (file:///Users/joulev/dev/www/webapps/node_modules/.pnpm/vite@4.1.4_@types+node@18.14.1/node_modules/vite/dist/node/chunks/dep-ca21228b.js:21737:20)
    at Object.resolveId (file:///Users/joulev/dev/www/webapps/node_modules/.pnpm/vite@4.1.4_@types+node@18.14.1/node_modules/vite/dist/node/chunks/dep-ca21228b.js:21488:28)
    at Object.handler (file:///Users/joulev/dev/www/webapps/node_modules/.pnpm/vite@4.1.4_@types+node@18.14.1/node_modules/vite/dist/node/chunks/dep-ca21228b.js:44872:19)
    at file:///Users/joulev/dev/www/webapps/node_modules/.pnpm/rollup@3.17.1/node_modules/rollup/dist/es/shared/node-entry.js:24163:40
    at async PluginDriver.hookFirstAndGetPlugin (file:///Users/joulev/dev/www/webapps/node_modules/.pnpm/rollup@3.17.1/node_modules/rollup/dist/es/shared/node-entry.js:24063:28)
    at async resolveId (file:///Users/joulev/dev/www/webapps/node_modules/.pnpm/rollup@3.17.1/node_modules/rollup/dist/es/shared/node-entry.js:23007:26)
    at async ModuleLoader.resolveId (file:///Users/joulev/dev/www/webapps/node_modules/.pnpm/rollup@3.17.1/node_modules/rollup/dist/es/shared/node-entry.js:23271:15)
    at async Object.resolveId (file:///Users/joulev/dev/www/webapps/node_modules/.pnpm/vite@4.1.4_@types+node@18.14.1/node_modules/vite/dist/node/chunks/dep-ca21228b.js:7972:10)

[dotansimha]

This package is type-only package, and does not include any code.
@n1ru4l any idea if we should adjust the config in bob?

[n1ru4l]

@dotansimha Should be supported by bob. 🤔 https://github.com/kamilkisiela/bob/pull/144/files#diff-691ec73579d989528bc5e4a7db013c029b3c478b3360d962ad5548a0ce42d1c1

I'll have a look.

[enisdenjo]

Hey @joulev, thanks for reporting this!

However, I have not been able to replicate this - I'll keep trying but in the meantime; have you tried a clean install (remove node_modules recursively and run install again)? Maybe share more info like the package.json, or ideally a repro?

[joulev]

@enisdenjo Thanks for the reply. I retried just now with all node_modules removed and reinstalled, but the same thing happened.

My repo is a SvelteKit Vite app, where this package is used as part of GraphQL codegen; it's available here if you want a repro repo right now, but since it's a monorepo I will create a repro repo as minimal as possible instead, and will get back to you in a few hours.

[enisdenjo]

Thank you very much! That will help out definitely. In the meantime, I will try out a few things. 👍

[joulev]

@enisdenjo Reproduction repo

Sorry as it might not be as minimal as you expected it to be, but I am not confident enough to make it any more minimal.

For the repo, if you run pnpm install and pnpm build it will fail. Changing the version of @graphql-typed-document-node/core to v3.1.1 fixes the build error.

[enisdenjo]

Vite is having issues importing @graphql-typed-document-node/core as a value, it worked with v3.1.1 because there we had an empty file that we used for value imports - but this changes. Am looking into ways of handling this.

A proper approach would also be to use type imports for type-only modules, I made a PR here: joulev/debug#1.

[joulev]

Thank you, it worked. (Don't worry about the deployment failure; it was because I didn't configure Vercel to build SvelteKit in that repo.)

Since I intend to keep the debug repo as-is so future people can come to this issue and see the reproduction repo as when it was reported, I think I will close your PR and commit to the main repo instead (see above).

[websitevirtuoso]

The plugin "vite:dep-scan" was triggered by this import

script:/home/viktord/Projects/renthome/dashboard/src/modules/notifications/modules/NotificationsBtnDeleteAll.vue?id=0:26:7:
  26 │ import '@graphql-typed-document-node/core'
     ╵        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I started to get this error as well. I have no idea what happened but it worked many month and stopped

[websitevirtuoso]

you can try adding an exclusion rule for the @graphql-typed-document-node/core package in your Vite configuration. vite.config.js

It will help till this package will be fixed or vite will be fixed

export default {
  // ...other config options

  optimizeDeps: {
    exclude: ['@graphql-typed-document-node/core'],
  },
};

[emj365]

For pnpm:

pnpm i graphql @graphql-typed-document-node/core
pnpm i -D typescript ts-node @graphql-codegen/cli @graphql-codegen/client-preset

https://the-guild.dev/graphql/codegen/docs/guides/react-vue#installation