-
Notifications
You must be signed in to change notification settings - Fork 114
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
Package types is not being resolved in a TS setup when moduleResolution
is bundler
#2480
Comments
A video demo: CleanShot.2023-12-10.at.09.40.09.mp4 |
Confirmed adding the types to the export sections fixes this. Wondering if we can do a shorter PR in the interim to just add these? |
The package.json of
The problem is that the version of the bundler lib doesn't include this feature. Meaning that the only solution would be upgrading it. |
I was able to workaround this issue with a quick and dirty solution using patch-package and diff --git a/node_modules/graphql-modules/package.json b/node_modules/graphql-modules/package.json
index 3feda76..d37c95f 100644
--- a/node_modules/graphql-modules/package.json
+++ b/node_modules/graphql-modules/package.json
@@ -30,7 +30,8 @@
"exports": {
".": {
"require": "./index.js",
- "import": "./index.mjs"
+ "import": "./index.mjs",
+ "types": "./index.d.ts"
},
"./*": {
"require": "./*.js", |
same problem here |
Any updates on this? This is killing my ci/cd pipeline :/ |
This worked perfectly! |
Describe the bug
I've noticed that when using
graphql-modules
in a TypeScript project that definesmoduleResolution: "bundler"
:TypeScript cannot resolve the type definitions:
That's because in the generated
dist/package.json
, thetypes
field is not present in theexports
condition:I won't write all the details here because I saw you're using a tool called
bob
to generate the final dist, and the problem is there.I just opened this issue to keep it as a reminder so that when this problem is fixed on the
bob
's side, you can upgrade it and generate a release.To Reproduce
Expected behavior
Working without a problem in TS configs where it defines the
moduleResolution
equalsbundler
Environment:
graphql-modules
: 2.3.0Additional context
The text was updated successfully, but these errors were encountered: