Impit crashed itself and the reason it crashed that i cant understand

[IamsadVN]

i was using impit@0.7.4 (the latest version from NPM) in a JS project.

i started the script i made in TS and built it to JS and it run normally, sometime the proxy IP blocked me or something so they threw an error about the request timeout

but in the end of the image, impit threw an error that i has never seen it before, and it crashed my script.

i dont know how to fix it, or really dont know how to catch this error to make it not possible to crash my script anymore.

what is this error and how can i fix it? or do i need to wait another impit version?

[barjin]

Hello and thank you for your interest in this project!

Please share a minimal reproduction scenario. Without this, we cannot assist you further.

Cheers!

[IamsadVN]

Here is the complete explanation of how I am using your impit package, as requested.

In my project, I need to query a large number of pixel coordinates from an external API. For each pixel, I must use a different proxy, so my script creates a new Impit instance for every request. The usage pattern looks like this:

1. For each pixel request, I create a new Impit instance with the following options:

   • proxyUrl (rotated on every request),
   • timeout: 6000,
   • browser: "firefox",
   • ignoreTlsErrors: true,
   • http3: true.
     This means my script may instantiate Impit thousands of times during a full scan.

2. After creating the instance, I call impit.fetch("https://place34.com/api/pixel/...").
   If fetch throws an error (which happens often with unstable proxies), I retry the same request inside a loop until it completes without an exception. The logic is essentially:
   “try fetch, and if it fails, repeat again using the same instance.”

3. In the main execution flow, I build a list of pixel requests and execute them in batches of 50.
   This results in multiple Impit instances running concurrently — typically around 50 at a time.
   Each batch is awaited with Promise.all.

4. When a request finally succeeds, I check response.ok, parse the JSON if available, and write the result to a text file.
   If it is not painted, I log that information instead.

So in summary, my usage pattern is:

• One new Impit instance per request (because each request needs a different proxy).
• Multiple instances running in parallel (50 per batch).
• Each instance may retry fetch several times until it resolves without throwing.
• The process repeats for a large number of pixel coordinates, resulting in many instantiations of Impit.

This is the scenario that leads to the issue I reported.
If you need the exact code or more details, I can provide them as well.

(disclaimer: i used GPT to translate + describe what my code look like to tell you how my code is running)

[barjin]

Hello and thank you for your response (and sorry for the delay).

Unfortunately, I cannot replicate the issue locally. Could you please share an actual code snippet (preferably calling a local server) that reproduces this issue?

Thank you!