Running tsc on this project leads to a bunch of errors about conflicts between node_modules/typescript/lib/lib.dom.d.ts and node_modules/@cloudflare/workers-types/2022-11-30/index.d.ts.
I have discovered a workaround - creating an empty file and remapping the path in tsconfig's compilerOptions:
However, it seems like cross-fetch/polyfill shouldn't be specifying a specific types, and should instead be relying on tsconfig to include the appropriate types (either via lib or types).
148 seems to have introduced a regression of sorts when using a library which has its own definitions of types used by
fetch
.The following code worked fine with earlier versions, but it appears that the introduction of
types
topolyfill/package.json
causes some conflicts to occur: https://github.com/lquixada/cross-fetch/blob/1fb2350e9e26bdc1a7903b8d5d051828503fbff6/polyfill/package.json#L7Here is an example project.
package.json
tsconfig.json
index.ts
Running
tsc
on this project leads to a bunch of errors about conflicts betweennode_modules/typescript/lib/lib.dom.d.ts
andnode_modules/@cloudflare/workers-types/2022-11-30/index.d.ts
.I have discovered a workaround - creating an empty file and remapping the path in tsconfig's
compilerOptions
:However, it seems like
cross-fetch/polyfill
shouldn't be specifying a specifictypes
, and should instead be relying ontsconfig
to include the appropriate types (either vialib
ortypes
).