Dav

I am also facing this issue, I can recommend trying out patch-package so that it won't block you. Install patch-package: https://www.npmjs.com/package/patch-package Add the npm scripts section: `"postinstall": "patch-package"` Copy this...

I can also confirm Wulawa's answer, just install `customize-cra@next` and it works just fine. See the diff here: https://github.com/arackaf/customize-cra/compare/next I'm not very confident on the author fixing this issue with...

You can get around that like this to tsconfig: ``` { "extends": "./tsconfig.paths.json", //

@barronwei Did you manage to get a fix on this?

Noticed this is old but it is still an issue with firebase v9.9.3 and @firebase/rules-unit-testing v2.0.4 so it would be good to see an update or a fix here

Thanks @xbreaker that worked great until node-fetch updated to v3.1.0 now. The dependencies changed (https://github.com/node-fetch/node-fetch/blob/v3.1.0/package.json#L65) so the transformIgnorePatterns needs updating to include them ``` transformIgnorePatterns: [ 'node_modules/(?!(data-uri-to-buffer|formdata-polyfill|fetch-blob|node-fetch)/)', ] ``` There...

Just to give a bit more info here. node-fetch v2.6.1 allowed this: ```ts const mySpecialUrl = new URL('http://google.com'); return fetch(mySpecialUrl); ``` Now it gives a TS error since fetch is...

@jimmywarting from a quick test in Chrome browser (using native browser fetch) I see the url can be passed as a `new URL()`  I believe node-fetch should act the...

> We are already acting as the browser I disagree, the browser will let me pass a URL instance, node-fetch will not as it fails the TS definition. node-fetch has...

> Using `url.toString()` would weird, isn't? This is my (hopefully 🤞) short term solution, I would like to revert this commit once node-fetch updates the TS signature. I don't think...