1.4.0 breaks GraphQL
See original GitHub issueWhat version of Remix are you using?
1.4.0
Steps to Reproduce
Excerpt from package.json
"dependencies": {
"@chakra-ui/react": "1.8.8",
"@emotion/react": "11.9.0",
"@emotion/styled": "11.8.1",
"@fortawesome/fontawesome-svg-core": "6.1.1",
"@fortawesome/pro-light-svg-icons": "6.1.1",
"@fortawesome/pro-regular-svg-icons": "6.1.1",
"@fortawesome/pro-solid-svg-icons": "6.1.1",
"@fortawesome/react-fontawesome": "0.1.18",
"@graphql-tools/schema": "8.3.8",
"@graphql-tools/utils": "8.6.7",
"@hookform/resolvers": "2.8.8",
"@prisma/client": "3.12.0",
"@remix-run/express": "1.3.4",
"@remix-run/node": "1.3.4",
"@remix-run/react": "1.3.4",
"@welldone-software/why-did-you-render": "7.0.1",
"apollo-server-express": "3.6.7",
"authorizenet": "1.0.8",
"aws-sdk": "2.1116.0",
"chalk": "4.1.2",
"compression": "1.7.4",
"crypto-js": "4.1.1",
"dataloader": "2.1.0",
"debug": "4.3.4",
"dotenv": "16.0.0",
"express": "4.17.3",
"framer-motion": "6.3.0",
"gm": "1.23.1",
"graphql": "16.3.0",
"graphql-relay": "0.10.0",
"graphql-type-json": "0.3.2",
"jsonwebtoken": "8.5.1",
"lodash": "4.17.21",
"luxon": "2.3.1",
"morgan": "1.10.0",
"nanoid": "3.3.2",
"nodemailer": "6.7.3",
"object-hash": "3.0.0",
"papaparse": "5.3.2",
"pino": "7.10.0",
"pluralize": "8.0.0",
"prisma": "3.12.0",
"react": "17.0.2",
"react-dom": "17.0.2",
"react-hook-form": "7.29.0",
"react-router-dom": "6.3.0",
"react-virtual": "2.10.4",
"tailwindcss": "3.0.24",
"validator": "13.7.0",
"zod": "3.14.4"
},
"devDependencies": {
"@remix-run/dev": "1.3.4",
"@tailwindcss/aspect-ratio": "0.4.0",
"@tailwindcss/forms": "0.5.0",
"@tailwindcss/line-clamp": "0.3.1",
"@tailwindcss/typography": "0.5.2",
"@types/authorizenet": "1.0.0",
"@types/graphql": "14.5.0",
"@types/jest": "27.4.1",
"@types/node": "17.0.24",
"@types/react": "17.0.43",
"@types/react-dom": "17.0.14",
"@types/tailwindcss": "3.0.10",
"@typescript-eslint/eslint-plugin": "5.19.0",
"@typescript-eslint/parser": "5.19.0",
"autoprefixer": "10.4.4",
"dotenv-cli": "5.1.0",
"esbuild": "0.14.36",
"esbuild-register": "3.3.2",
"eslint": "8.13.0",
"eslint-config-airbnb": "19.0.4",
"eslint-config-airbnb-typescript": "17.0.0",
"eslint-config-prettier": "8.5.0",
"eslint-import-resolver-typescript": "2.7.1",
"eslint-plugin-import": "2.26.0",
"eslint-plugin-jsx-a11y": "6.5.1",
"eslint-plugin-prettier": "4.0.0",
"eslint-plugin-react": "7.29.4",
"eslint-plugin-react-hooks": "4.4.0",
"eslint-plugin-sort-destructure-keys": "1.4.0",
"eslint-plugin-sort-keys-fix": "1.1.2",
"jest": "27.5.1",
"npm-check": "5.9.2",
"pm2": "5.2.0",
"postcss": "8.4.12",
"postcss-cli": "9.1.0",
"postcss-import": "14.1.0",
"prettier": "2.6.2",
"prettier-plugin-tailwindcss": "0.1.8",
"ts-jest": "27.1.4",
"typescript": "4.6.3"
},
Expected Behavior
No errors 😃
Actual Behavior
This is the error I get:
server-2 | Error: Cannot use GraphQLObjectType "Address" from another module or realm.
server-2 | Ensure that there is only one instance of "graphql" in the node_modules
server-2 | directory. If different versions of "graphql" are the dependencies of other
server-2 | relied on modules, use "resolutions" to ensure only one version is installed.
server-2 | https://yarnpkg.com/en/docs/selective-version-resolutions
server-2 | Duplicate "graphql" modules cannot be used at the same time since different
server-2 | versions may have different capabilities and behavior. The data from one
server-2 | version used in the function from another could produce confusing and
server-2 | spurious results.
server-2 | at instanceOf2 (/Users/ivolution/Sites/koop/node_modules/graphql/jsutils/instanceOf.js:43:19)
server-2 | at isObjectType (/Users/ivolution/Sites/koop/node_modules/graphql/type/definition.js:131:26)
server-2 | at printType (/Users/ivolution/Sites/koop/node_modules/graphql/utilities/printSchema.js:134:23)
server-2 | at /Users/ivolution/Sites/koop/node_modules/graphql/utilities/printSchema.js:59:28
server-2 | at Array.map (<anonymous>)
server-2 | at printFilteredSchema (/Users/ivolution/Sites/koop/node_modules/graphql/utilities/printSchema.js:59:14)
server-2 | at printSchema2 (/Users/ivolution/Sites/koop/node_modules/graphql/utilities/printSchema.js:31:10)
server-2 | at Object.<anonymous> (/Users/ivolution/Sites/koop/app/graphql/index.server.ts:85:61)
server-2 | at Module._compile (node:internal/modules/cjs/loader:1101:14)
server-2 | at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
server-2 | Error: Cannot use GraphQLObjectType "Address" from another module or realm.
server-2 | Ensure that there is only one instance of "graphql" in the node_modules
server-2 | directory. If different versions of "graphql" are the dependencies of other
server-2 | relied on modules, use "resolutions" to ensure only one version is installed.
server-2 | https://yarnpkg.com/en/docs/selective-version-resolutions
server-2 | Duplicate "graphql" modules cannot be used at the same time since different
server-2 | versions may have different capabilities and behavior. The data from one
server-2 | version used in the function from another could produce confusing and
server-2 | spurious results.
server-2 | at instanceOf2 (/Users/ivolution/Sites/koop/node_modules/graphql/jsutils/instanceOf.js:43:19)
server-2 | at isObjectType (/Users/ivolution/Sites/koop/node_modules/graphql/type/definition.js:131:26)
server-2 | at printType (/Users/ivolution/Sites/koop/node_modules/graphql/utilities/printSchema.js:134:23)
server-2 | at /Users/ivolution/Sites/koop/node_modules/graphql/utilities/printSchema.js:59:28
server-2 | at Array.map (<anonymous>)
server-2 | at printFilteredSchema (/Users/ivolution/Sites/koop/node_modules/graphql/utilities/printSchema.js:59:14)
server-2 | at printSchema2 (/Users/ivolution/Sites/koop/node_modules/graphql/utilities/printSchema.js:31:10)
server-2 | at Object.<anonymous> (/Users/ivolution/Sites/koop/app/graphql/index.server.ts:85:61)
server-2 | at Module._compile (node:internal/modules/cjs/loader:1101:14)
server-2 | at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
The error happens when I call printSchema
from graphql
Downgrading to 1.3.4 fixes the issue.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:8 (2 by maintainers)
Top Results From Across the Web
1.4.0 breaks graphiql · Issue #158 · absinthe-graphql ... - GitHub
BUT WITHOUT RESTARTING the server graphiql still works fine. Restart and I get below. Actual behavior. [info] GET /graphiql [info] Sent 500 in ......
Read more >1.4.0 - Orchard Core Documentation
This release contains security vulnerability fixes. It is recommended you update your existing Orchard Core deployments with this version.
Read more >graphql-request - NPM Package Overview - Socket.dev
Minimal GraphQL client supporting Node and browsers for scripts or simple apps. Version: 5.0.0 was published by jasonkuhrt.
Read more >r/typescript - Zeus 1.4.0 - GraphQL Query Library - Reddit
Zeus 1.4.0 - GraphQL Query Library - now autocomplete support Unions! ... The make-or-break question for me is: can I use Zeus in ......
Read more >Relay
That means you won't accidentally break other components as you refactor or ... To get the most from Relay's features, you'll want your...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve narrowed it down to having a folder
app/graphql
that is accessible through a TypeScript global import with~/*
and in one of my route files I am doingand the
remix@1.4.0
after the removal of the postinstall script is treating it as a duplication somehow.This issue has been automatically closed because we haven’t received a response from the original author 🙈. This automation helps keep the issue tracker clean from issues that are unactionable. Please reach out if you have more information for us! 🙂