Alex Rickabaugh

Are you sure you installed local versions of _all_ Angular packages? I think for us to investigate this, you'll need to provide a repo that demonstrates the issue.

A workaround is to cast `description` in your template via `$any`. I agree, this is a bug and something we should address. One interesting idea would be to modify the...

Hi @aerojas. The `--lazy-root` flag (default value `src`) can tell `ngu-sw-manifest` which path to use to resolve lazy routes. To get your templates working correctly, you need to specify `moduleId:...

@aerojas thanks for the feedback! I'm not surprised `--lazy-root` didn't work if some of your `loadChildren` routes were absolute paths, I don't believe the tool supports those.

Hi @markgoho, Your error is the result of having two different versions of Angular installed. `npm ls | grep @angular` should show you.

@alfredoperez thank you! Yarn should ensure you get the exact same set of versioned packages as in the demo. Currently there are peer dep errors but those can be ignored....

Hey guys! That's some awesome debugging/workaround development! I should have some time to update `ng-pwa-tools` soon. I'll try to focus on windows support and some more documentation.

Which version of `firebase` do you have installed?

Hi @GregOnNet, thanks for the issue report. I don't think this will work anyway - `ngu-app-shell` does not support `.sass` input (because Angular does not). If your SASS code happens...

@alfredoperez make sure all of your components have `moduleId: module.id` in their metadata. All Angular CLI components should already follow this. I will do some testing on Windows to make...