No "exports" main defined in node_modules/got-scraping/package.json

[Battlesquid]

I'm trying to use got-scraping in a project. I have it imported asynchronously as specified in the README, however when I run my code, I get the following output.

node:internal/errors:484
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in C:\Users\battl\Documents\repos\testing\node_modules\got-scraping\package.json
    at new NodeError (node:internal/errors:393:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:340:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:564:7)
    at resolveExports (node:internal/modules/cjs/loader:492:36)
    at Module._findPath (node:internal/modules/cjs/loader:532:31)
    at Module._resolveFilename (node:internal/modules/cjs/loader:941:27)
    at Module._load (node:internal/modules/cjs/loader:803:27)
    at Module.require (node:internal/modules/cjs/loader:1021:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at C:\Users\battl\Documents\repos\testing\dist\scrape.js:38:132 {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Node.js v18.9.0

Research led me to this discussion which had the same issue I'm having, but unlike that user, I cannot migrate to ESM. What could I be doing wrong that would be causing this issue?

Here is a minimal reproducible example to illustrate the issue I'm having.

[Battlesquid]

Solved the issue, changing the module value in tsconfig.json to Node16 was the solution.