fix: cross-fetch version

[LuizAsFight]

cross-fetch 3.1.8 is breaking when using chrome extension executing requests inside service worker

overriding it to 4.0.0 fixed the problem

ref: cross-fetch

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟢	Statements	84.48%	4721/5588
🟡	Branches	62.85%	636/1012
🟡	Functions	68.68%	752/1095
🟢	Lines	84.61%	4526/5349

Test suite run success

1074 tests passing in 184 suites.

Report generated by 🧪jest coverage report action from eba36fb

[github-actions]

This PR is published in NPM with version 0.0.0-pr-1113-20230725000501

[arboleya]

CI was not passing; hitting "update branch" appears to have fixed it.

[arboleya]

Would it be possible to move the override to some packages/*/package.json instead of having it globally set on the root package.json?

I wonder what package uses such an outdated cross-fetch version from before Oct 5, 2020.

[LuizAsFight]

Would it be possible to move the override to some packages/*/package.json instead of having it globally set on the root package.json?

I wonder what package uses such an outdated cross-fetch version from before Oct 5, 2020.

graphql-request latest uses it.

[arboleya]

Good find! Indeed, they're using this outdated version, there's this issue about it.

For now, we could still move the overriding inside the provider package.

Congrats on this hotfix, @LuizAsFight!

[LuizAsFight]

@arboleya

https://pnpm.io/package_json#pnpmoverrides

Note that the overrides field can only be set at the root of the project.