pnpm dev works... but pnpm build breaks app... Any ideas?

[frankmayer]

Hi,
as the title says.
pnpm dev works... but pnpm build breaks app.

When directly requesting any page with graphql data, it responds with:
500 Unexpected error..

When browsing indirectly (by browsing to another page an then clicking to go to any graphql data page) it shows the page but with undefined values.

the error is as follows:

{
  "errors": [
    {
      "message": "Unexpected error.",
      "extensions": {
        "originalError": {
          "message": "Cannot use GraphQLSchema \"{ __validationErrors: undefined, description: undefined, extensions: undefined, astNode: { kind: \"SchemaDefinition\", operationTypes: [Array] }, extensionASTNodes: [], _queryType: Query, _mutationType: Mutation, _subscriptionType: undefined, _directives: [@include, @skip, @deprecated, @specifiedBy], _typeMap: { Category: Category, ID: ID, String: String, Review: Review, Int: Int, User: User, Version: Version, Mutation: Mutation, addCategoryInput: addCategoryInput, addReviewInput: addReviewInput, Query: Query, Date: Date, DateTime: DateTime, Product: Product, Float: Float, Boolean: Boolean, addProductInput: addProductInput, ProductsFilterInput: ProductsFilterInput, __Schema: __Schema, __Type: __Type, __TypeKind: __TypeKind, __Field: __Field, __InputValue: __InputValue, __EnumValue: __EnumValue, __Directive: __Directive, __DirectiveLocation: __DirectiveLocation }, _subTypeMap: {}, _implementationsMap: {} }\" from another module or realm.\n\nEnsure that there is only one instance of \"graphql\" in the node_modules\ndirectory. If different versions of \"graphql\" are the dependencies of other\nrelied on modules, use \"resolutions\" to ensure only one version is installed.\n\nhttps://yarnpkg.com/en/docs/selective-version-resolutions\n\nDuplicate \"graphql\" modules cannot be used at the same time since different\nversions may have different capabilities and behavior. The data from one\nversion used in the function from another could produce confusing and\nspurious results.",
          "stack": "Error: Cannot use GraphQLSchema \"{ __validationErrors: undefined, description: undefined, extensions: undefined, astNode: { kind: \"SchemaDefinition\", operationTypes: [Array] }, extensionASTNodes: [], _queryType: Query, _mutationType: Mutation, _subscriptionType: undefined, _directives: [@include, @skip, @deprecated, @specifiedBy], _typeMap: { Category: Category, ID: ID, String: String, Review: Review, Int: Int, User: User, Version: Version, Mutation: Mutation, addCategoryInput: addCategoryInput, addReviewInput: addReviewInput, Query: Query, Date: Date, DateTime: DateTime, Product: Product, Float: Float, Boolean: Boolean, addProductInput: addProductInput, ProductsFilterInput: ProductsFilterInput, __Schema: __Schema, __Type: __Type, __TypeKind: __TypeKind, __Field: __Field, __InputValue: __InputValue, __EnumValue: __EnumValue, __Directive: __Directive, __DirectiveLocation: __DirectiveLocation }, _subTypeMap: {}, _implementationsMap: {} }\" from another module or realm.\n\nEnsure that there is only one instance of \"graphql\" in the node_modules\ndirectory. If different versions of \"graphql\" are the dependencies of other\nrelied on modules, use \"resolutions\" to ensure only one version is installed.\n\nhttps://yarnpkg.com/en/docs/selective-version-resolutions\n\nDuplicate \"graphql\" modules cannot be used at the same time since different\nversions may have different capabilities and behavior. The data from one\nversion used in the function from another could produce confusing and\nspurious results.\n    at instanceOf (/dev/node_modules/.pnpm/graphql@15.8.0/node_modules/graphql/jsutils/instanceOf.js:35:13)\n    at isSchema (/dev/node_modules/.pnpm/graphql@15.8.0/node_modules/graphql/type/schema.js:42:34)\n    at assertSchema (/dev/node_modules/.pnpm/graphql@15.8.0/node_modules/graphql/type/schema.js:46:8)\n    at validateSchema (/dev/node_modules/.pnpm/graphql@15.8.0/node_modules/graphql/type/validate.js:42:28)\n    at assertValidSchema (/dev/node_modules/.pnpm/graphql@15.8.0/node_modules/graphql/type/validate.js:66:16)\n    at validate (/dev/node_modules/.pnpm/graphql@15.8.0/node_modules/graphql/validation/validate.js:51:35)\n    at Object.validate (file:///dev/node_modules/@envelop/core/esm/orchestrator.js:164:26)\n    at processRequest (file:///dev/node_modules/graphql-yoga/esm/processRequest.js:34:15)\n    at YogaServer.getResultForParams (file:///dev/node_modules/graphql-yoga/esm/server.js:280:32)\n    at processTicksAndRejections (node:internal/process/task_queues:95:5)"
        }
      }
    }
  ]
}

The graphql version is 15.8.0 (also in the resolutions)

Any ideas why this happens and how I can debug this? Any config I can set to get more information about th error?

Thank you

[frankmayer]

So, solved this myself, given the time....
In the past I had checked the node-linker=hoisted option in .npm, but it had given me problems with other modules not updating etc, so I went for not using that option. It turns out this was causing the problem.

So, I went for including individual packages, but those things in the past did also bring trouble... but.... turns out the trouble was actually because while testing out the different hoisted - nonhoisted, dependencies and their versions, the package stores were getting corrupted and while I was mostly prune(ing) (and store prune(ing) them, sometimes I also needed to do full deletes. While this was going on I wasn't very consistent in cleaning up, so I might have gotten some false positives in there, as in "did not work for me".

So my solution (at least for now) is:

1. have all the @kitql/all-in-one dependencies in my project dependencies
2. To be safe from any corruptions, delete my pnpm store (yes the main pmpn one), by finding it with pnpm store path and removing the store
3. pnpm i in your project (other projects based on the deleted store will also have to pnpm i)
   Hope this helps anyone.
   If you have different experiences or issues with that, pls write in this discussion and we'll try to help.

[jycouet]

Could you let me know what version are you using?

[frankmayer]

Hi @jycouet , sure:
pnpm: 7.14.0

• dependencies block with node-linker=hoisted

		"@kitql/all-in@: "0.8.0-next.15",
		"@kitql/module-codegen": "0.4.0-next.1",
		"graphql": "^15.8.0",
		"vite-plugin-watch-and-run": "1.1.0-next.4"

• dependencies block with individual dependencies at the moment (and all-in removed) those:

		"@envelop/core": "3.0.2",
		"@envelop/graphql-modules": "4.0.2",
		"@graphql-codegen/cli": "2.13.7",
		"@graphql-codegen/graphql-modules-preset": "2.5.3",
		"@graphql-codegen/introspection": "2.2.1",
		"@graphql-codegen/typed-document-node": "2.3.4",
		"@graphql-codegen/typescript": "2.7.4",
		"@graphql-codegen/typescript-resolvers": "2.7.4",
		"@graphql-eslint/eslint-plugin": "3.12.0",
		"@graphql-typed-document-node/core": "3.1.1",
		"@kitql/helper": "0.6.0-next.3",
		"@kitql/module-codegen": "0.4.0-next.1",
		"glob": "^8.0.3",
		"graphql": "^15.8.0",
		"graphql-config": "^4.3.6",
		"graphql-modules": "^2.1.0",
		"graphql-scalars": "^1.20.0",
		"graphql-yoga": "3.0.0-next.5",
		"safe-stable-stringify": "^2.4.1",
		"ts-node": "^10.9.1",
		"vite-plugin-watch-and-run": "1.1.0-next.4"

did you mean that?

[frankmayer]

BTW, I am "all-in" (pun intended 😄 ) for an "all-in" way, for beginners to start with, but a way that doesn't lead to issues when used with pnpm.

On the other hand for individual packages in project's dependencies:

• pros for using individual packages is of course more flexibility
• cons is of course the added responsibility of tracking versions, etc. But for production, I'd probably go for individual.

[jycouet]

The all point of this lib KitQL is to ensure that everything is working together.
If you have to manually do things, somehow I failed.

The issue is that npm / yarn 1 / yarn 3 / pnpm have some differences... I should probably test all of them :(
I'll try to exit the next version this week anyway with a "stable" thing. 🤞

Thx for your inputs 👍