-
Notifications
You must be signed in to change notification settings - Fork 233
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
Consider using @angular/service-worker and ng-pwa-tools #68
Comments
I have the documentation in a form of workshop currently: https://bit.ly/pwa-angularsummit-2017 |
Unfortunately, there is no way to go for simplest default option to set up NGSW (to use |
@Splaktar Thank you so much for logging this, I've been meaning to set up an issue to use Angular's built in tools instead of @webmaxru <3 thank you!! Yep I decided to eject in order to modify the build output so we can't unfortunately rely on setting |
I wrote a special notice on For now I'm struggling with |
@webmaxru very helpful, thank you. There is indeed quite a bit of confusion and the presentation didn't do enough to mention how experimental ng-pwa-tools is at this point. |
Agreed that is extremely helpful @webmaxru <3 Thank you for taking the time to look into the tools deeper and explaining it clearly! |
@webmaxru although we can't simply use |
I haven't tried the |
I created an application using ng-PWA-tools, most of the code from @housseindjirdeh and setting up gulp to do some performance adjustments; since I didn't eject the angular-cli. Can all of you take a look and tell me how I can improve it? https://www.webpagetest.org/result/170710_YC_e36dbf524b1105e6a05b9c7b90d20668/
Any help is appreciated! My goal is to make it faster using some of the techniques other apps used, like Firebase functions, compression, server rendering, while still keeping the angular cli intact. |
This project is using sw-precache instead of the latest
@angular/service-worker
andng-pwa-tools
.At Google I/O last week, they announced that https://github.com/GoogleChrome/workbox would be the preferred option over sw-precache going forward.
However, Angular seems to be creating a better integrated SW and PWA story using the tools mentioned above. That said, it would be interesting to see if these tools actually reduce the size of the config and improve performance or load time.
The text was updated successfully, but these errors were encountered: