-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Running Workbox in DEBUG mode #10555
Comments
I have the same question. |
The author of the pwa template answered in cra-template/pwa#15 that it can't be easily done. I think it'll be tremendously helpful if CRA can add this option as an environmental variable in Here is the doc page about the debugging mode, which seems not applicable to CRA. |
Thanks @ZYinMD I did reach out to him and he gave me a similar response. I decided to post this still to see if it is something worth evaluating by the community. |
I don't think that's strictly true, at least not for someone who wrote the code. They just don't want to, because they don't think you should be using service workers for anything but dumb caching. Maybe Safari support is still horrible so they don't want people complaining about "why CRA doesn't work with Safari"? |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
Is there an option or a way to run service-worker (generated by workbox) in debug mode?
It seems like workbox checks
process.env.NODE_ENV !== 'production'
before logging any debug messages...and we currently only run
WorkboxWebpackPlugin
whenisEnvProduction
is true.Is this intentional, if not what will the best way to give developers a way to debug their service-worker?
The text was updated successfully, but these errors were encountered: