maciejtreder / ng-toolkit

:star: Angular tool-box! Start your PWA in two steps! Add Serverless support for existing projects and much more

@ng-toolkit

This project has two faces:

• First, a Angular Universal PWA boilerplate, prepared for easy deployment on Serverless environment. The boilerplate contains all of the best practices and is continously evolving. Find out more about the boilerplate here.
• Second, a collection of schematics (used with the ng add command) which can be applied to existing Angular projects. All schematics comes from the boilerplate mentioned above. The main goal is to make those schematics interchangeably (developer can apply them in any order)!

Wanna be a server-side Angular hero?

If you want to sharpen your skills in Angular Universal or you won't find what you're looking for in this project; check out the Guide to Angular Universal written by me for Newline.co!

Content

• What's inside
  • Application starter/boilerplate
  • Angular Universal/server-side rendering
  • Serverless support (Firebase, AWS Lambda, Google Cloud Functions)
• Planned features
• Question, Problem, Feature Request
• Support @ng-toolkit

What's inside

PWA starter

npm install -g @ng-toolkit/init
ng new --collection @ng-toolkit/init myApp [--provider --firebaseProject --gaTrackingCode --firebug]

• Read more documentation

PWA - @angular/pwa extension

Add update mechanism and server-side rendering fixes to your PWA

ng add @ng-toolkit/pwa [--serverModule]

• Read more documentation

Serverless (Firebase, AWS Lambda, Google Cloud Functions)

Make your app deployable on serverless environment (FaaS)

ng add @ng-toolkit/serverless [--provider --firebaseProject]

• Read more documentation
• Read article about serverless with @ng-toolkit

Angular Universal

Add server-side rendering and improve SEO of your app

ng add @ng-toolkit/universal

• Read more documentation
• Read article about server-side rendering with @ng-toolkit

Firebug-lite

Add firebug-lite to your Angular app

ng add @ng-toolkit/firebug

• Read more documentation

Planned features

• @ng-toolkit/googleAnalytics - tracking user and JS exceptions in Google Analytics
• @ng-toolkit/compodoc - introduce compodoc - documentation tool for your angular app
• @ng-toolkit/safariPush - add pushes for Safari users

Looking for something more?

Feel free to create issue with your feature request

Support @ng-toolkit

You can support development of this project via:

• Open Collective
• Donorbox
• Liberapay
• Paypal

If you want, you can be listed on the List of donors on the demo page.

Open Collective Backers

Thank you to all our backers! 🙏 [Become a backer]

Open Collective Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

Credentials

• Checkout my home page and find out more about me

ng-toolkit's Issues

Provide support for meta tags.

new push notification service breaks Safari

Depends on
angular/angular#20407

No SEO?

Hi, and let me start by saying thank you for this amazing project! I tried to fork and use it and even upgraded it to the latest Angular version. But then a major drawback struck me in the face. There is no SEO :(

I mean, the server-side generated pages do not have any of the text you see when you load the page with JavaScript. The means that search engines will also not see the text of any of the modules, not even a homepage, just a generic template that's the same for every page.

Also, I've got a question about external modules. What good are they if we still need to recompile the whole app when that module changes in a different directory somewhere on GitHub?

Thanks!

FormsModule Not working

I'm submitting some data but ngValue,ngModel not working here is my code

code home-component.ts

  import { NgForm } from '@angular/forms';

code home-component.html

    < div class="col-md-2">
        < select *ngIf="segment.breathCycle.length > 1" [(ngModel)]="segment.selectedDuration">
         < option *ngFor="let d of segment.breathCycle;" [ngValue]="d">{{d.breathCycleDuration}}
              < /select>
            < /div>

code app.modulet.ts

import { FormsModule, ReactiveFormsModule } from '@angular/forms';

@NgModule({
    declarations: [
        AppComponent,
        NavComponent
    ],
    imports: [
        MatButtonModule,
        MatSnackBarModule,
        MatMenuModule,
        TranslateModule.forChild(),
        CommonModule,
        HttpModule,
        FormsModule,
        RouterModule.forRoot([
            // { path: '/', component: DashboardComponent },
            { path: 'home', component: DashboardComponent }
        ]),
        HttpClientModule,
        PrebootModule.withConfig({ appRoot: 'app-root' })
    ],
    providers: [SnackBar, WindowRef,HttpService, Notifications, HitWithTransferStateResolver, HitWithoutTransferStateResolver, ExampleApi, Title, Meta],

    bootstrap: [AppComponent]
})

I am following this

npm install -g angular-universal-pwa
ng new --collection angular-universal-pwa myApp
cd myApp
npm start

I was start today. When I run npm start It's working good, but when I run npm run build:prod for server I am getting error Please Solve this

Thank you

Error

Invalid AMP HTML

Passing the demo through the AMP Validator, it seems that AMP errors on the following:

• All custom attributes like _ngcontent-c0 - and an Angular app is full of those in order to emulate a native ViewEncapsulation
• All custom tags (<app>, <mat-menu>, <my-component> etc.)

There a a lot of other things as well, plus the repo is AMP only. In my experience, you would have an AMP version along side the regular version.
But the biggest problem right now would be the above 2 points that I have no idea how to avoid. Setting ViewEncapsulation.None would mean that all your component styles would become global.
Also, I don't think there's anybody that would be willing to give up using custom tags + tag selector for Angular components, and go with class selectors.

Not sure if new version of app is replacing old one

mobile device support

blocked by AhsanAyaz/ngx-device-detector#15

error when creating new project

I'm submitting a...

[x] Bug report  
[ ] Feature request
[ ] Documentation issue or request

Current behavior

$ ng new --collection angular-universal-pwa ngPwa
Schematic "ng-new" not found in collection "angular-universal-pwa".
Error: Schematic "ng-new" not found in collection "angular-universal-pwa".
    at SchematicEngine.createSchematic (/home/bkinsey/.nvm/versions/node/v9.11.1/lib/node_modules/@angular/cli/node_modules/@angular-devkit/schematics/src/engine/engine.js:155:23)
    at CollectionImpl.createSchematic (/home/bkinsey/.nvm/versions/node/v9.11.1/lib/node_modules/@angular/cli/node_modules/@angular-devkit/schematics/src/engine/collection.js:12:29)
    at NodeWorkflow.execute (/home/bkinsey/.nvm/versions/node/v9.11.1/lib/node_modules/@angular/cli/node_modules/@angular-devkit/schematics/tools/workflow/node-workflow.js:70:38)
    at Promise (/home/bkinsey/.nvm/versions/node/v9.11.1/lib/node_modules/@angular/cli/models/schematic-command.js:134:22)
    at new Promise (<anonymous>)
    at NewCommand.runSchematic (/home/bkinsey/.nvm/versions/node/v9.11.1/lib/node_modules/@angular/cli/models/schematic-command.js:133:16)
    at NewCommand.<anonymous> (/home/bkinsey/.nvm/versions/node/v9.11.1/lib/node_modules/@angular/cli/commands/new.js:77:25)
    at Generator.next (<anonymous>)
    at /home/bkinsey/.nvm/versions/node/v9.11.1/lib/node_modules/@angular/cli/commands/new.js:7:71
    at new Promise (<anonymous>)

Expected behavior

Minimal reproduction of the problem with instructions

npm i -g @angular/cli
npm i -g @angular-devkit/schematics
npm i -g angular-universal-pwa

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z

Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: 8,9
- Platform:  Ubuntu

Others:

clicking on 'launch' new version should reload application

Static Files S3

Hello, could you please elaborate a bit more on the subject of why you're not using S3 to store the static files?
It would be much cheaper or not? Especially with multiple bundles and async loading.

main styles are not loaded in development mode

ios scrolling

Error on npm start

Output said to let you know, here is my debug log - any help would be appreciated! Thanks!!!

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 silly lifecycle [email protected]~prestart: no script for prestart, continuing
7 info lifecycle [email protected]~start: [email protected]
8 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/ec2-user/workspace/angular-universal-serverless/node_modules/.bin:/sbin:/bin:/usr/sbin:/usr/bin
10 verbose lifecycle [email protected]~start: CWD: /home/ec2-user/workspace/angular-universal-serverless
11 silly lifecycle [email protected]~start: Args: [ '-c', 'npm run build && npm run server' ]
12 silly lifecycle [email protected]~start: Returned: code: 1  signal: null
13 info lifecycle [email protected]~start: Failed to exec start script
14 verbose stack Error: [email protected] start: `npm run build && npm run server`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:891:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid [email protected]
16 verbose cwd /home/ec2-user/workspace/angular-universal-serverless
17 error Linux 4.9.27-14.31.amzn1.x86_64
18 error argv "/usr/bin/node" "/usr/bin/npm" "start"
19 error node v6.11.0
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error [email protected] start: `npm run build && npm run server`
22 error Exit status 1
23 error Failed at the [email protected] start script 'npm run build && npm run server'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the angular-universal-serverless package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     npm run build && npm run server
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs angular-universal-serverless
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls angular-universal-serverless
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

AWS Lambda

Hello,
So i have an existing app which has universal. I installed serverless and also added additional packages in package.json.

package.json

"dependencies": {
    "aws-serverless-express": "3.0.0"
},
"devDependencies": {
    "serverless": "^1.21.1",
    "serverless-apigw-binary": "^0.4.0"
}

I copied lambda.js and serverless.yml to the root of the directory.

Is this all needed to deploy? because when i run serverless deploy, it deploys but when i goto the url i get

{
message: "Internal server error"
}

firebug should not be downloaded when schematics are installed

I'm submitting a...

[ x ] Bug report  
[ ] Feature request
[ ] Documentation issue or request

Current behavior

after running npm install -g angular-universal-pwa firebug is downloaded and an attempt to unpack is done

Expected behavior

firebug should be downloaded only once, when project is installed

Tracking code in google analytics should be configurable

I'm submitting a...

[ ] Bug report  
[ x ] Feature request
[ ] Documentation issue or request

Current behavior

Tracking code is hardcoded

Expected behavior

Tracking code should be taken from environment.ts

Error: Cannot find module '../dll/vendor-manifest.json'

Hello I am trying to start the application from scratch in a Docker container but when I run the command npm start I am getting the following error:

`
module.js:471
throw err;
^
Error: Cannot find module '../dll/vendor-manifest.json'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at module.exports (/my-app/webpack/webpack.common.js:12:27)
at module.exports (/my-app/webpack.config.js:20:45)
at handleFunction (/my-app/node_modules/webpack/lib/prepareOptions.js:26:13)
at prepareOptions (/my-app/node_modules/webpack/lib/prepareOptions.js:11:13)
at requireConfig (/my-app/node_modules/webpack/bin/convert-argv.js:98:14)
at /my-app/node_modules/webpack/bin/convert-argv.js:104:17
at Array.forEach (native)
at module.exports (/my-app/node_modules/webpack/bin/convert-argv.js:102:15)
at Object. (/my-app/node_modules/webpack-dev-server/bin/webpack-dev-server.js:223:50)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)

npm info lifecycle [email protected]~webdev: Failed to exec webdev script
npm ERR! Linux 4.4.0-96-g`

Step to Reproduce

• Login into Docker Playground (https://labs.play-with-docker.com/) and start an instance

• Run the following coomand:

  git clone https://github.com/maciejtreder/angular-universal-pwa.git
  cd angular-universal-pwa

• Create the following Dockefile

  FROM node:6.10
  LABEL "author"="uolter"

  RUN apt-get update && apt-get install git -y

  COPY . /my-app
  WORKDIR /my-app

  RUN npm install

  EXPOSE 300
  ENTRYPOINT ["npm", "start"]

• Build the application:

  docker -t build uolter/angular-universal-pwa:latest

• Run the application:

  docker run -it --rm --name angular-universal -p 3000:3000 uolter/angular-universal-pwa:latest

Have I missed something?
Can you help me to understand why I am getting this error?

Add to home screen button

I'm submitting a...

[ ] Bug report  
[x] Feature request
[ ] Documentation issue or request

Expected behavior

Rewrite the application for it do display a "Add to home screen" button on the front page of the application given a compatible browser is used (Desktop browser will soon support this feature from what I've read; Chrome already does if the corresponding flag is activated).

Here's a video tutorial on YouTube on how to do this with Angular Universal:
https://www.youtube.com/watch?v=C1Pji5XvXbE

Cannot run from subfolder

The way this project now works locally is great but as soon as I deploy it as AWS Lambda, it goes into a subfolder called "production" - which is automatic and cannot be overridden from what I can see. This breaks the project because it tries to load all assets from the root folder.

Introduce Schematics for CLI

I'm submitting a...

[ ] Bug report  
[ x ] Feature request
[ ] Documentation issue or request

Current behavior

No schematics support

Expected behavior

Introduce schematics ;)

Demo API usage in the application

The most challenging part of SSR/Universal application is the API integration, where the API should not be called after the bootstrapping of the framework. This is done using TransferState. Can you add a page for that use case in this app?

Translations question

Hi!

Nice to see you're making progress and integrating the FireBug stuff - that's quite a nice touch there :)
I tried to implement translations via https://www.npmjs.com/package/@ngx-translate/core but that only worked for the local server and failed for the AOT compiled one. Would you have any experience in implementing this, please? I would really appreciate a nudge in the right direction. All the code does now is returning a textual "Error" line on the page and nothing else, so I'm kinda stuck on what could this be causing.

I'm basically using this to accomplish the translation: https://www.npmjs.com/package/@ngx-translate/core#aot

I've just spent so much time trying to debug and solve this that I'm willing to put up a donation for you if you'd be able to take the time to help me with this one :)

Cheers and good work on this project!

Unit tests

I'm submitting a...

[ x ] Bug report  
[ x ] Feature request
[ ] Documentation issue or request

Current behavior

Lack of unit tests

Expected behavior

After upgrade to CLI (#144) unit tests need to be reimplemented

Postinstall fails

I have postinstall script failing. Getting the same error via npm/yarn on different node versions.

    ERROR in ./$$_lazy_route_resource lazy
    Module not found: Error: Can't resolve '/Users/rooticalv/Projects/WKL/angular-universal-pwa/node_modules/@angular-universal-serverless/external-module/release/src/externalComponent/external.module.ngfactory.js' in '/Users/rooticalv/Projects/WKL/angular-universal-pwa/$$_lazy_route_resource'
     @ ./$$_lazy_route_resource lazy
     @ ./node_modules/@angular/core/esm5/core.js
     @ dll vendor

    ERROR in ./$$_lazy_route_resource lazy
    Module not found: Error: Can't resolve '/Users/rooticalv/Projects/WKL/angular-universal-pwa/src/app/lazy/lazy.module.ngfactory.js' in '/Users/rooticalv/Projects/WKL/angular-universal-pwa/$$_lazy_route_resource'
     @ ./$$_lazy_route_resource lazy
     @ ./node_modules/@angular/core/esm5/core.js
     @ dll vendor

    ERROR in src/app/windowRef.ts(1,25): error TS2307: Cannot find module '@nguniversal/express-engine/tokens'.

main.scss reloading is not working in development mode

Error on production build

When checking out the project and running it in production mode (npm run build:prod && npm run server) i get the following javascript error:

Uncaught Error: No NgModule metadata found for 'e'. at e.resolve (client.js:1) at e.getNgModuleMetadata (client.js:1) at e._loadModules (client.js:1) at e._compileModuleAndComponents (client.js:1) at e.compileModuleAsync (client.js:1) at e.compileModuleAsync (client.js:1) at e.bootstrapModule (client.js:1) at r (client.js:1) at i (client.js:1) at Object.a (client.js:1)

This however is not the case when i run it with npm start (Dev build). What am i doing wrong?

Cannot read property 'config' of null

What to do ?

Angular CLI: 1.6.7
Node: 8.5.0
OS: win32 x64
Angular: 5.2.3
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic
... platform-server, router, service-worker

@angular/app-shell: 0.1.0
@angular/cdk: 5.2.0
@angular/cli: 1.6.7
@angular/material: 5.2.0
@angular-devkit/build-optimizer: 0.0.42
@angular-devkit/core: 0.0.29
@angular-devkit/schematics: 0.0.52
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.7
@schematics/angular: 0.1.17
typescript-collections: 1.3.2
typescript: 2.7.1
webpack-dev-server: 2.11.1
webpack-merge: 4.1.1
webpack: 3.10.0

notification service & menu component cleanup

This code is spaghetti...

window-ref on serverside

I'm submitting a...

[ x ] Bug report  
[ x ] Feature request
[ ] Documentation issue or request

Current behavior

Lack of windowRef on server side

Expected behavior

After upgrade to CLI (#144) windowRef must be fixed

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z


Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

firebug should be downloaded only when it is not present in the file system

I'm submitting a...

[ x ] Bug report  
[ ] Feature request
[ ] Documentation issue or request

Current behavior

Every call to npm install cause redownload of firebug.

Expected behavior

Firebug should be downloaded and decompressed only when it is not present in the filesystem

Should work also with development link

App should not support only customized URLs

Can't resolve moduleName.ngfactory.js

When setup my angular4 theme and try to deploy on aws serverless gives these errors. But localy it works fine. Please help me.

Prod Server Build

When I run the npm run server command and load http://localhost:8080 I'm redirected to https://www.angular-universal-pwa.maciejtreder.com/

I checked the main.server.js file and updated the app.get('/**', (req, res) => {..... command, however, on a fresh build, still getting redirected?

Local updates therefore not getting reflected. Anything obvious I;m missing?

Thanks in advance...

production build doesn't work

I'm submitting a...

[ x ] Bug report  
[ ] Feature request
[ ] Documentation issue or request

Current behavior

Several issues are thrown by production build

introduce back external module

I'm submitting a...

[ x ] Bug report  
[ x ] Feature request
[ ] Documentation issue or request

Current behavior

Lack of support for external modules

Expected behavior

After upgrade to CLI (#144) external module support must be fixed

Introduce tests

google analytics support should be optional

I'm submitting a...

[ ] Bug report  
[ x ] Feature request
[ ] Documentation issue or request

Current behavior

google analytics is always installed

Expected behavior

user should be able to define if he want to use GA. Also it should be a possibility to add it later via '''ng g''' command.

Doesn't render properly on iOS

slow reload

So as per your suggestion i moved to this starter because i could not make the serverless work on the previous starter. Reloading is very slow in this starter, i changed 1 line of css and it did whole build which was very time consuming.

provide support for progressive web app

google cloud

great repo! thanks...

would you please guide how I can modify this starter to use google cloud as serverless backend in stead of aws?

perhaps, you may want to provide a configuration option to use either aws/azure/google cloud

many thanks

Preboot to replay all the actions on the site

I'm submitting a...

[ ] Bug report  
[x] Feature request
[ ] Documentation issue or request

Current behavior

Preboot is not used, so actions taken before the bootstrap of the application are wasted

Expected behavior

All the actions taken while loading of javascript should be replayed

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z


Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

sticky footer

Fresh everything on local: build:prod then server creates error below

I'm pretty sure this is related to my local environment? Everything is a fresh install with supplied packages and versions. build:prod then server creates the error:

Uncaught Error: No NgModule metadata found for 'e'.
at e.resolve (client.js:formatted:29517)
at e.getNgModuleMetadata (client.js:formatted:27173)
at e._loadModules (client.js:formatted:35989)
at e._compileModuleAndComponents (client.js:formatted:35966)
at e.compileModuleAsync (client.js:formatted:35910)
at e.compileModuleAsync (client.js:formatted:17009)
at e.bootstrapModule (client.js:formatted:5234)
at r (client.js:formatted:13813)
at i (client.js:formatted:36630)
at Object.a (client.js:formatted:13859)

The build:prod seems to work fine with only a couple warnings.

The material buttons do not seem to render as a result and navigating pages does not load the content.

Again, I'm suspecting this is related to my local environment as I see the live demo is working correctly.

I love what I'm seeing with this so far, I just need to debug this little issue and it looks like everything else is working great.

Should not overwrite default .angular-cli config file

I'm submitting a...

[ x ] Bug report  
[ ] Feature request
[ ] Documentation issue or request

Current behavior

When using ng new, original CLI config file is overwritten by custom one - those effect in lack of possibility of changing some CLI options during project initialization.

Expected behavior

All CLI custom settings should be in the project config

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z


Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

Provide support for angular material

Angular CLI 6.x

I'm submitting a...

[ ] Bug report  
[ x ] Feature request
[ ] Documentation issue or request

Expected behavior

Newest CLI should be supported

main.ts file should be removed/overwritten

I'm submitting a...

[ x ] Bug report  
[ ] Feature request
[ ] Documentation issue or request

Current behavior

CLI creates redundant main.ts file.

Expected behavior

This file should be removed by schematics

introduce back ng-http-sw-proxy

Depends on webmaxru/pwatter#2

Angular CLI support

I'm submitting a...

[ ] Bug report  
[x] Feature request
[ ] Documentation issue or request

Current behavior

There is no Angular CLI support

Expected behavior

As more devs are using CLI, it would be great to introduce it to this repo.