Cannot find name 'ErrorOptions'.

Question

Cannot find name 'ErrorOptions'.

ohonigx opened this issue 2 years ago · 19 comments

Hi,

via

"@zxing/library": {
"version": "0.19.1",
"resolved": "https://registry.npmjs.org/@zxing/library/-/library-0.19.1.tgz",
"integrity": "sha512-rKwvl3Uuqs8yf364iU9l3HDDaIx8yPv+CH6DbtQaQr67VdKLG22G1ukEp9fOdDefE6tpLtRAdMnTrgtpiaKAZw==",
"requires": {
"@zxing/text-encoding": "~0.9.0",
"ts-custom-error": "^3.0.0"
}
},

i got a new

      ERROR in node_modules/ts-custom-error/dist/custom-error.d.ts:3:45 - error TS2304: Cannot find name 'ErrorOptions'.

today.

i can't find any ErrorOptions class here and the github universe, please help,
thanks

Answer 1 · 2022-10-24T11:43:34.000Z

also i've had this error today , when i find 3.3.0 was released, turning back to 3.2.2 solved, anyway i think that ErrorOptions interface came from typescript compiler options about libs, you shuld try to add in lib section of the compiler options "ES2022.error"

Answer 2 · 2022-10-24T12:28:03.000Z

Same issue here :/

Answer 3 · 2022-10-24T13:26:22.000Z

Same issue here, can't compile my angular9 project since using zxing 3.3.0.

Answer 4 · 2022-10-24T13:26:42.000Z

I've encountered the same issue because we're using @zxing/library, which references any version >=3.0.0
Changing the version in the package.lock to 3.2.2 fixed this temporarily.

Answer 5 · 2022-10-24T15:27:30.000Z

Sooooory, please, rollback to 3.2.2 or add "ES2022" & "ES2022.error" in your tsconfig.json lib array. thanks @f-mon for the quick & efficient solution.
I'm really sorry, I introduced this bug while adding a new feature, see #38

Answer 6 · 2022-10-24T22:20:06.000Z

package.json
"ts-custom-error":"3.2.2",
and all is fine again ..

Answer 7 · 2022-10-25T16:53:46.000Z

I've deprecated version 3.3.0 , put back the 3.2.2 as current version.

I'll see how to fix properly this issue with a 3.3.1 version ASAP

Answer 8 · 2022-10-25T17:01:11.000Z

@ohonigx

i can't find any ErrorOptions class here and the github universe, please help,

it's from https://github.com/microsoft/TypeScript/blob/main/lib/lib.es2022.error.d.ts

yep, it's a thing ;)

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause

https://v8.dev/features/error-cause

But now I have to find an elegant way to introduce it without breaking your builds ;)

Answer 9 · 2022-10-25T17:21:00.000Z

@ohonigx

But now I have to find an elegant way to introduce it without breaking your builds ;)

:-) Thanks to the others here i solved it with the new entry in package.json "ts-custom-error":"3.2.2", so the zxing/library is happy again. Thanks for your work and the fast reponse!

Answer 10 · 2022-10-27T08:20:57.000Z

Hi, @adriengibrat

we use dependency "@zxing/ngx-scanner": "3.0.0", which still creates the following in package_lock.json`:
"@zxing/library": {
"version": "0.15.2",
"resolved": "https://registry.npmjs.org/@zxing/library/-/library-0.15.2.tgz",
"integrity": "",
"requires": {
"text-encoding": "^0.7.0",
"ts-custom-error": "^3.0.0"
},
"dependencies": {
"ts-custom-error": {
"version": "3.3.0",
"resolved": "https://registry.npmjs.org/ts-custom-error/-/ts-custom-error-3.3.0.tgz",
"integrity": ""
}
}
},
"@zxing/ngx-scanner": {
"version": "3.0.0",
"resolved": "https://registry.npmjs.org/@zxing/ngx-scanner/-/ngx-scanner-3.0.0.tgz",
"integrity": "",
"requires": {
"@zxing/library": "^0.15.1",
"tslib": "^1.9.0"
},
"dependencies": {
"tslib": {
"version": "1.14.1",
"resolved": "https://registry.npmjs.org/tslib/-/tslib-1.14.1.tgz",
"integrity": ""
}
}
},

Seems it still considers 3.3.0 as the latest.

I tried npm i ts-custom-error in some other place and it still shows,
"dependencies": {
"ts-custom-error": "^3.3.0",
}

I think it still recognize 3.3.0 as latest.

Answer 11 · 2022-10-27T09:38:56.000Z

Hello I have the same problem as @RandulaKoralage . We use @zxing/ngx-scanner which underneath uses @zxing/library which uses "ts-custom-error": "^3.0.0". Therefore I cannot edit this dependency

On my rather new npm it is handled correctly, i.e. deprecated module is skipped and last correct version is installed.

However, on other place where my npm is quite old and I cannot update, it keeps taking the deprecated version and therefore the build fails

Could you completely remove the version 3.3.0 from npm? If the lib is broken then it does not help anyone. Is there any other reason why it still needs to be kept in npm repository?

Regards
Antoni

Answer 12 · 2022-10-31T07:27:56.000Z

in React, @zxing/library still installs 3.3.0, so I installed "ts-custom-error" v3.2.2 as a dev dependency.
npm i -dev ts-custom-error@3.2.2

Answer 13 · 2022-11-01T13:11:56.000Z

For all those who still have issue because dependency tree still install 3.3.0,

you may try to
upgrade typescript >=4.6
& add :
"lib: [...,"ES2022", "ES2022.error"],
in your tsconfig.json

see https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-6.html#--target-es2022

Answer 14 · 2022-11-01T13:28:18.000Z

Unfortunately it is not an option for me. My current version of Angular does not allow to upgrade typescript to that version and upgrading Angular is also not possible for me at the moment.

Answer 15 · 2022-11-01T20:24:20.000Z

I've released a 3.3.1 version where i copy the typescript ErrorOption interface to avoid the error, I hope this should definitively fix the issue.

Answer 16 · 2022-11-01T20:30:38.000Z

Please, confirm the 3.3.1 compiles on your projects, then i'll close the issue.

Answer 17 · 2022-11-02T07:20:16.000Z

My build works again! :) thank you

Answer 18 · 2022-11-02T09:51:15.000Z

Finally! @adriengibrat my build also worked. Thank you.

Answer 19 · 2022-11-02T21:13:55.000Z

OK, it's fixed. Thanks for your feedback.