-
Notifications
You must be signed in to change notification settings - Fork 43
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
Fix importing types on Node 16 module resolution #424
Fix importing types on Node 16 module resolution #424
Conversation
Thanks a lot! Could you squash and sign-off, please, so we can get this merged? Details here |
Signed-off-by: Phillip Huang <[email protected]>
Signed-off-by: Phillip Huang <[email protected]>
Signed-off-by: Phillip Huang <[email protected]>
1a9203e
to
17a330c
Compare
mv $outdir/types/opa.d.ts $outdir/types/opa.d.mts | ||
cp $outdir/types/opa.d.mts $outdir/types/opa.d.cts |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately separate declaration files are required. Otherwise, typescript will assume the types are either ESM or CJS depending on the value of the type
field of the nearest package.json.
Any updates on getting this merged? |
Hello @srenatus - is there anything I can do to help get this out? |
@JavaScriptBach Are you around? To get this merged, it'll need your sign-off. |
Oh wait, this has sign-offs on each commit. Nevermind. I'll take care of rebasing and pushing a new release. |
Fixes #332
I upgraded my TypeScript moduleResolution to Node 16, and TypeScript stopped being able to find the types. This change should fix it.