[@types/request] Error: has no exported member named 'CookieJar' #71418

Thanks for the discussion about "request", some useful links for everyone:

• npm
• DT
• Related discussions

Pinging the DT module owners: @soywiz, @bonnici, @Bartvds, @joeskeen, @ccurrens, @lookfirst, @mastermatt, @josecolella, @murbanowicz.

I'm having the same issue.

Same issue

Also seeing this issue when running tsc using tough-cookie 5.0.0.

Any updates on a fix?

Hello everyone, we got a legacy project assigned to our team and facing the same error:

node_modules/tough-cookie/dist/cookie/index"' has no exported member named 'CookieJar'. Did you mean 'Cookie'?

setCookie(cookieOrStr: Cookie | string, uri: string | Url, options?: tough.CookieJar.SetCookieOptions): void;

Thank you!

I encountered the same issue when I tried running a legacy project. Any help would be welcomed.

I have the same issue.

It prevented my project from building, so I had to modify build script with --skipLibCheck flag:

// package.json
"build": "tsc --skipLibCheck", 

but it's just muting warning, so real fix would be appreciated.

Also facing this issue when building a legacy app. Any help would be appreciated.

Same thing here, been trying everything under the sun to try and fix this to no avail.

facing the same issue here as well.. unable to get past this issue.

Facing the same issue after upgrading from from jsdom@24 to jsdom@26 which is using tough-cookie@5.1.1

Facing the same issue with jsdom please help

"skipLibCheck": true - tsconfig

tough.CookieJar is no longer exported from tough-cookie@5.x.x
installing a previous version solved my problem

npm i tough-cookie@4.1.4

Hey all, seems like this issue is still persistent. For now, we have an override in our package.json to pin tough-cookie to 4.1.4, but this seems like an unsustainable fix for the long term. Can we get some advice on a proper fix, or is there another PR that is working to address this? It seems like from the PR linked above there was an alternate fix that the DefinitelyTyped team recommended, but it's not clear what the status is on that.

Just one more +1 for this problem. For us, I preferred to pin "@types/request": "2.0.0" (many years old) since it didn't have the offending @types/tough-cookie dep at all, and yet didn't lead to any other tsc issues. Could perhaps have yarn patched the package.json or something instead, but this was at the level of "just make it work", to move the offending thing out of the way.

One more +1. Now I have problem with angular 22, airbrake/browser and @types/request.