Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Types out of date #32

Open
Quantumplation opened this issue May 12, 2020 · 4 comments
Open

Types out of date #32

Quantumplation opened this issue May 12, 2020 · 4 comments

Comments

@Quantumplation
Copy link

Upgraded chrome typings recently, and now chrome-promise is failing with the following errors:

/srv/package/node_modules/chrome-promise/chrome-promise.d.ts
ERROR in /srv/package/node_modules/chrome-promise/chrome-promise.d.ts(73,51):
TS2694: Namespace 'chrome.accessibilityFeatures' has no exported member 'AccessibilityFeaturesGetArg'.
/srv/package/node_modules/chrome-promise/chrome-promise.d.ts
ERROR in /srv/package/node_modules/chrome-promise/chrome-promise.d.ts(73,118):
TS2694: Namespace 'chrome.accessibilityFeatures' has no exported member 'AccessibilityFeaturesCallbackArg'.
/srv/package/node_modules/chrome-promise/chrome-promise.d.ts
ERROR in /srv/package/node_modules/chrome-promise/chrome-promise.d.ts(81,51):
TS2694: Namespace 'chrome.accessibilityFeatures' has no exported member 'AccessibilityFeaturesSetArg'.
/srv/package/node_modules/chrome-promise/chrome-promise.d.ts
ERROR in /srv/package/node_modules/chrome-promise/chrome-promise.d.ts(89,53):
TS2694: Namespace 'chrome.accessibilityFeatures' has no exported member 'AccessibilityFeaturesClearArg'.
@Quantumplation
Copy link
Author

Looks like the relevant commit is here:

DefinitelyTyped/DefinitelyTyped@f34693c#diff-825aab95db5570e43fc04346c6b2971e

@Quantumplation
Copy link
Author

Last version that worked, for anyone coming across this issue:

"@types/chrome": "0.0.96",

I personally don't depend on anything changed since then, but I'm sure it'll become a problem for people eventually.

@tscislo
Copy link

tscislo commented Oct 1, 2022

@Quantumplation can you recommend any alternative that this compatible with latest Chrome?

@tscislo
Copy link

tscislo commented Oct 2, 2022

If anybody is still wondering... apparently this lib is not longer needed with Chrome manifest v3, because all Chrome APIs are already promisified. So basically there is no need for this library. @Quantumplation @tfoxy. Currently I only use it for backwards compatibility for chrome extensions that still run manifest v3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants