-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
PWA does not work with workbox / typescript (maybe a feature request?) #8340
Comments
|
Exclude folder {
"extends": "@quasar/app/tsconfig-preset.json",
"compilerOptions": {
"..."
},
"exclude": [
"src-pwa"
]
} |
I tried that, but unfortunately it gives me another error (see https://forum.quasar-framework.org/topic/7495/pwa-typescript/4#):
|
I hate this error. Get it very in often in Webstorm but not when building for dev or prod. Try the following:
{
"extends": "./tsconfig.json",
"include": [
"src/**/*.js",
"src/**/*.ts",
"src/**/*.vue",
"types/*.ts",
"types/**/*.ts",
"*.js"
]
}
|
@razorness thanks for the hint, I applied it to https://github.com/sluedecke/quasar-pwa-test/commit/2d39572261348d02b630037be142ecaaf6fff364 , but it still is not working:
|
PWA with Typescript will be available through |
As time will allow me, I'll backport to Quasar v1 as well. |
Migration path to Quasar v2 is a bit too heavy for our application now, but using TS in Is it possible to help to backport the feature to Quasar v1? |
Describe the bug
Want to implement custom-service-worker using workbox recipies.
Codepen/jsFiddle/Codesandbox (required)
Sample repository: https://github.com/sluedecke/quasar-pwa-test
To Reproduce
Steps to reproduce the behavior:
yarn install
quasar build --mode pwa
Expected behavior
Project builds without errors
Screenshots
If applicable, add screenshots to help explain your problem.
Platform (please complete the following information):
Operating System - Linux(5.10.7-arch1-1) - linux/x64
NodeJs - 15.6.0
Global packages
NPM - 6.14.11
yarn - 1.22.10
@quasar/cli - 1.1.3
Additional context
This has also been discussed here:
The text was updated successfully, but these errors were encountered: