Alex Rickabaugh

@Splaktar as I mentioned before, SCSS is not supported by Angular as a whole - being able to reference it directly is Angular CLI specific functionality.

@cars10 in that case, you can not pass `--module` to `ngu-sw-manifest`, and instead write your routing configuration manually. The fundamental problem here is that all of the `ngu-` tools require...

@webmaxru looks good to me! In general I think it'd be very useful to document supported/unsupported cases. The tooling can then be made smarter by making it detect things which...

This PR was merged into the repository by commit 86372538ab017058cb9b2a7910e761d823bd3c16.

@james-schwartzkopf, you can make the class non-abstract, and add it to the module that way. Or, as an alternative workaround, mark the abstract pipe with `@Injectable()`.

This PR was merged into the repository by commit 120555a626d66523e46ce01681b11a0f38e3a40a.

@JoostK I agree we should simply not allow private inputs in the first place. This has never been supported in Angular. Also, nothing actually is stopping us from _also_ generating...

There does seem to be something really weird with private inputs and template type-checking. This is worth working on further.

Hello @btakita, @alfaproject, Some questions for you both: 1) What's your environment? View Engine / Ivy? JIT / AOT? 2) Try serving with `ng serve --aot` and report the exact...

@IamDeshRaj, you rock! The root cause here is that `platformServer()` (and `platformBrowserDynamic` for that matter) expose a platform injector that provides `CompilerFactory` with `JitCompilerFactory`, which creates a View Engine compiler....