Using a HTTP proxy?

[jpstotz]

Is it possible to configure a HTTP proxy that will be used for the HTTP requests?

[baltpeter]

No, that is not currently possible but I'm happy to accept a PR implementing it.

Here's where the network requests happen:

parse-play/src/common/requests.ts

Lines 15 to 27 in 1e42ad9

	const res = await fetch(`https://play.google.com/_/PlayStoreUi/data/batchexecute${buildQueryString(queryParams)}`, {
	method: 'POST',
	headers: {
	'Content-Type': 'application/x-www-form-urlencoded;charset=utf-8',
	},
	// The (stringified) number at index 3 of each request is supposed to specify the order in which the responses
	// are returned (see: https://kovatch.medium.com/deciphering-google-batchexecute-74991e4e446c#ea4a). We want
	// them in the same order as the requests.
	//
	// From my testing, this doesn't always seem to be the case. But as the number is also returned in the response,
	// we can use it to manually sort the payloads later.
	body: `f.req=${encodeURIComponent(JSON.stringify([requests.map((r, idx) => [...r, null, '' + idx])]))}`,
	}).then((r) => r.text());

From a quick look, it seems like there is unfortunately an issue with cross-fetch's TypeScript types when using proxies (lquixada/cross-fetch#203).

[jpstotz]

Is cross-fetch really still necessary? As fetch is now supported natively since Node.js v21 in my understanding this package is no longer necessary?

[baltpeter]

At least for the time being, I would like to continue supporting older Node versions.

[jpstotz]

OK, I see Node.js 20 is a LTS release that has still support until Apr 2026, thus cross-fetch still makes sense.

Regarding a PR, I am sorry but your project exceeds my TypeScript knowledge, not the code but the project set-up. Just building and using your project requires detailed knowledge of the TypeScript build infrastructure as the way the project is using parcel ends up in an endless-loop of errors complaining what is prong in multiple of the used dependencies. Seems like the fast evolution of TypeScript has totally screwed the build process of older projects like this. Even with the help of ChatGPT I wasn't able to build and make use of the cloned parse-play package.