-
Notifications
You must be signed in to change notification settings - Fork 814
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
Many typescript issues while type checking #2642
Comments
There are some known linting issues with the latest TypeScript and eslint releases, tracked in #2602 Regarding some of the other issues, I would avoid using the Definitely Typed definitions for the Workbox v5 runtime modules, which are native TypeScript code and can be used directly. The errors about missing
in your service worker file, but
Hopefully that combination of answers gets things working for you! |
Thanks a lot, i will apply your recommendations and wait for workbox type def update |
There are many things broken right now, so don't trust this. References: <https://stackoverflow.com/questions/56356655/structuring-a-typescript-project-with-workers> <GoogleChrome/workbox#2642>
There are many things broken right now, so don't trust this. References: <https://stackoverflow.com/questions/56356655/structuring-a-typescript-project-with-workers> <GoogleChrome/workbox#2642> <https://gist.github.com/dsebastien/12c47fdb6517cfdab9473297f4472d22>
I'm adding workbox in my ReactJs application.
When i'm running Husky post-commit hooks with
tsc -p tsconfig.json --noEmit
, a lot of errors from workbox packages comes. If i runtsc -p tsconfig.json --noEmit --skipLibCheck
, as you know, errors disappearHere is my tsconfig.json :
Here is my service-worker entry point :
Here is my second entry point for my app, which import
workbox-window
:PS : Additionally, i'm falling into
@typescript-eslint/no-unsafe-member-access
andeslint-disable @typescript-eslint/no-unsafe-call
in the service-worker.ts too ... Even if i added @types/Here is my eslint config :
My dependencies :
😕
The text was updated successfully, but these errors were encountered: