-
Notifications
You must be signed in to change notification settings - Fork 805
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
Typescript confusion #2860
Comments
Hello! While it's true that I think that that's the standard way for library authors to deal with this sort of thing, and is therefore not something that we have plans to change. If I'm misunderstanding a use case, or if this breaks something for you, please let me know and we can reevaluate. |
That is true, only if you create the function inline. wb.addEventListener('waiting', handleWaiting) // error
wb.addEventListener('waiting', myClassInstance.handleWaiting) // error The first case is very common. This is very limiting |
Fair enough! We can get those event definitions exported as part of an upcoming Workbox v6 release. |
The fix is now deployed in a pre-release of Workbox v6.2.0: https://github.com/GoogleChrome/workbox/releases/tag/v6.2.0-alpha.0 |
Library Affected:
workbox-window
Browser & Platform:
"all browsers".*
Issue or Feature Request Description:
I'm trying to use
workbox-window
in Typescript however, the package doesn't export any event type declarations?WorkboxLifecycleWaitingEvent
is not exported fromworkbox-window
The text was updated successfully, but these errors were encountered: