-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[7.0.1] broken types #846
Comments
I opened an issue yesterday and it was closed, and many others, the issue is TypeScript compiler doesn't read the |
closing, duplicate: #844 |
@jasonkuhrt I believe we need the |
@efstathiosntonas but that issue got closed as well 🥲 |
@AbdUlHamedMaree how did you managed to solve this? can you share your |
@efstathiosntonas just change |
did that earlier and it breaks everything, got like 200 errors lol. @jasonkuhrt can you please bring the types back? It's a tremendous breaking change. |
oh yeah it did break the building process 🥲 |
Have you enabled |
And you need to have your TSConfig setup properly https://stackoverflow.com/questions/70296652/how-can-i-use-exports-in-package-json-for-nested-submodules-and-typescript |
@jasonkuhrt You're totally right, didn't expect |
This comment was marked as off-topic.
This comment was marked as off-topic.
@Zerebokep is that a runtime error or TS error. Looks like a runtime error. Confirm? If so, Node version? |
Yup, runtime, I'm using node 22.1.0. |
Then it's not about broken types. New issue welcome, thanks! |
Strangely it works on another container with a similar setup, I'm even using the same tsconfig there. Not sure if it's relevant, but I'm using pnpm as package manager and tsx to execute the script. I've also checked the package.json of graphql-request node_modules folder, it's identical for both containers, exports are included. |
After upgrading to
7.0.1
IDE complains about typings.Screenshot
Description
Reproduction Steps/Repo Link
The text was updated successfully, but these errors were encountered: