You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
node_modules/@apollo/server/dist/esm/externalTypes/plugins.d.ts:6:344 - error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './requestPipeline.js'?
When installing @apollo/server v4 in a TS project using "moduleResolution": "nodenext",
TS would throw errors about how Apollo Server's imports need to use extensions.
Specifically, we omitted extensions from all type-only imports since they didn't seem to
be needed, but it's not hurting anything to add them and some use cases require it.
Add a new smoke test for this use case which will ensure extensions are used in all
source code files, even for type-only imports.
Fixes#6730
Lots of errors like this:
Repro: https://codesandbox.io/s/musing-albattani-s8v12i
Looks like we just need extensions everywhere, not just runtime imports.
The text was updated successfully, but these errors were encountered: