shibbir / generator-angular2-typescript

Yeoman generator to scaffold out a front-end project with angular, typescript, webpack and much more..

Hi there 👋

I'm Shibbir, Web developer from Bangladesh, currently living in Germany.

Programming Languages

Database & ORMs

Framework & Libraries

Server & Runtime Environments

Tools

Latest writings

• Authentication with OpenID Connect
• Introduction To Webpack
• Introduction To Gulp
• Beginning RequireJS

How to reach me

generator-angular2-typescript's Issues

How to handle lazy loaded modules with SystemJS Builder?

In your Gulp file i see you use buildStatic to generate the production build, but you do not use lazy loading modules, provided by Angular2.

I'm developing an app based on your project and i added some modules in my application.
I created the following router configuration since i use lazy loading modules:

const appRoutes: Routes = [
	{ path: '', component: MainComponent,
	    canActivate: [AuthGuard],
	    children: [
	        { path: 'dashboard', component: DashboardComponent },
	        { path: 'first-section', loadChildren: 'app/modules/FIRST-SECTION/first-section.module' },
	        { path: 'second-section', loadChildren: 'app/modules/SECOND-SECTION/second-section.module' },
	        { path: 'documents', component: DocumentsComponent },
	        { path: 'users', component: UsersComponent },
	        { path: '', redirectTo: 'dashboard', pathMatch: 'full' }
	    ]
	}
];

Here is my Gulp task (similar to yours):

gulp.task('app-bundle', function() {
    var builder = new Builder('src', 'src/systemjs.config.js');

    return builder.buildStatic('app/main.js', 'build/scripts/app.min.js', { minify: true });
});

But... if i try to run a server on the build package the app doesn't work when it tried to run a path of the router that use a lazy loaded module. It gives me the following error:

GET http://127.0.0.1:8080/app/modules/FIRST-SECTION/first-section.module 404 (Not Found)

Do you know how can i use lazy loading modules with SystemJS Builder?

Gulp task to build Prod version with SystemJS

Hi, when i select gulp and System i can't find a task to build the final version of the app. How can i do it?

Foundation integration: does it work?

I installed the package selecting Foundation. Then I tried to use some Foundation code, but it doesn't work.
For example if I put inside the template of a component the code for creating a slider (http://foundation.zurb.com/sites/docs/slider.html) it doesn't work.

Why? Shouldn't it work? Otherwise why we import Foundation JS file?

source code generated not included karma config

source code generated not included karma config

Support for end-to-end testing with protractor

"ENOENT: no such file or directory" with production task

Hello, i tried to see the output of the production task and i run the build:prod task.
But i get some No such file or directory errors.

Here you can see the full log:

http://pastebin.com/2mHRAWW1

Provide a "None" option in addition to Bootstrap / Foundation?

That would be nice for the simplistic projects, or projects that do not agree with all the pieces in the bootstrap implementation.

Open for discussion and might be worth splitting but:

• If I'm using Bootstrap CSS with Angular 2, I'm less likely to use the bootstrap JS and jQuery.
  I might use something like ng2-bootstrap, or nothing at all
• Maybe I do not want bootstrap at all
• The current if usages in templates seem to be a bit hard to manage for a 3rd option.
  Looks like using a folder structure for these would be better, not sure.
  I haven't written the code though so maybe not a good judgement

404 returned when generated with systemjs and without gulp

Requested html files are not found by lite-server because there is no npm script that can copy the html,css,js files into dist directory which is configured as a base directory for lite-server.

Support async/await operators and use @types instead of typings

https://github.com/kraken97/angular2Aw
I create own config using your generator and add async/await.
It will be cool if your add option for async/await and
types manager @types or typings.

Add support for yarn

Use the offline compiler for Webpack

I discovered this gem the other day, ngc-loader, by one of the Webpack core team members.

Would it make sense to try to add it to the project? I asked the guy on twitter and he said that the AngularClass starter uses it (I couldn't see where), and he said a few other ones but didn't specify.

I realise you already try to do something related to precompilation, seeing some precompile property in the AppComponent's @Component.

Would that be a good idea, or you rather wait for Application Modules or something?

I think this one is usable now though. Still sharpening my own Webpack skills so not sure of all the details.

Couldn't select CSS framework

I couldn't select CSS framework using arrow keys, and eventually "none" was selected.
When i pressed down arrow key,nothing changes , it stopped at "None" and couldn't change the option.
But Module loader could be selected using arrow keys.

How do you launch correctly the server?

Hello,
I have installed the generator with Foundation and SystemJS, but when i launch "npm start" then a browser page opens i only see "Loading..." on the screen.
If i open the console i see this error

Error: patchProperty/desc.set/wrapFn@http://localhost:3000/node_modules/zone.js/dist/zone.js:769:27
    Zone</ZoneDelegate</ZoneDelegate.prototype.invokeTask@http://localhost:3000/node_modules/zone.js/dist/zone.js:356:24
    Zone</Zone</Zone.prototype.runTask@http://localhost:3000/node_modules/zone.js/dist/zone.js:256:29
    ZoneTask/this.invoke@http://localhost:3000/node_modules/zone.js/dist/zone.js:423:29

    Error loading http://localhost:3000/foundation-sites/dist/foundation.css as "foundation-sites/dist/foundation.css" from http://localhost:3000/app/app.component.js

So i am wondering if i'm missing something to run the application

I am using Windows 10, if it changes something

Support for unit testing with SystemJS

tsc and tsc -w

Hello, i installed your package with Yeoman and i had a look to gulpfile.js:

gulp.task('server', plugins.shell.task('tsc && concurrently \"npm run tsc:w\" \"npm run lite\" '));

Can you tell me why tsc run twice?
Isn't better run only tsc -w?

gulp.task('server', plugins.shell.task('concurrently \"npm run tsc:w\" \"npm run lite\" '));

And what about to add "compileOnSave": true, in tsconfig.json (as described here) in order to use tsc with no "watch mode"?

gulp.task('server', plugins.shell.task('concurrently \"npm run tsc\" \"npm run lite\" '));

Replace gulp with npm scripts?

Hello,
It's quite common for SystemJS and Webpack to completely replace gulp. So, matching the trends, etc. it might be a good idea to remove gulp. mostly for increasing user base, and to remove the question "Why do you have gulp when you also use systemJS/Webpack?".

The generator doesn't seem to be using gulp for much anyway. It should be possible to convert that into a few npm scripts. Maybe there will be another helper JS file, or might even get away without one.

Is this a welcome idea? Would you like to give it a go? Or prefer having a PR to evaluate?

Just starting the discussion, and happy to give it a go as PR if the idea in general is accepted.

Thanks.

PS

This is an AWESOME project. I love. Thanks heaps for creating it.

is it ready to be used in production?

Firstly thank you for your amazing work.. it gives me a head start. But is it ready to be used in production release and angular version you are using is 2.0.0 and there many newer releases

Unable to debug on vscode

I am trying to debug Typescript on vscode using this launch.json

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch Chrome against localhost, with sourcemaps",
            "type": "chrome",
            "request": "launch",
            "url": "http://localhost:3000",
            "sourceMaps": true,
            "webRoot": "${workspaceRoot}"
        },
        {
            "name": "Attach to Chrome, with sourcemaps",
            "type": "chrome",
            "request": "attach",
            "port": 9222,
            "sourceMaps": true
        }
    ]
}

The connection works but the breakpoints don't (“Breakpoint ignored becasue generated code not found”).

do I have to specify the directory where the .map files are?

Javascript / Typescript sourceMap not working on Firefox with Webpack

Hi,
I've asked this question on StackOverflow: http://stackoverflow.com/questions/39973108/sourcemap-not-working-on-firefox-with-webpack-on-angular-2-application

I can't correctly see line numbers while on Firefox, i'm pretty sure it's a Firefox bug but i was wondering if there's something that can be done to fix it "code side"

Doesn't work out of the box

-- Fix seems to be to force reflect-metadata to 0.1.3, the current version (0.1.4) appears to be broken. Proposed change which fixes up the solution.

Done a simple install using webpack, gulp and foundation, run the default gulp task and get the following errors:

C:\source\temp4>gulp
(node:4736) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
[11:11:11] Using gulpfile C:\source\temp4\gulpfile.js
[11:11:11] Starting 'default'...
[11:11:11] Starting 'clean:dist'...
[11:11:11] Finished 'clean:dist' after 3.1 ms
[11:11:11] Starting 'server'...
70% 3/3 build moduleshttp://localhost:3000/
webpack result is served from http://localhost:3000/
content is served from C:\source\temp4
404s will fallback to /index.html
44% 4/7 build modulests-loader: Using [email protected] and C:\source\temp4\tsconfig.json
chunk {0} app.js, app.css (app) 6.43 kB {2} [rendered]
chunk {1} polyfills.js, polyfills.css (polyfills) 769 kB [rendered]
chunk {2} vendor.js (vendor) 3.3 MB {1} [rendered]

WARNING in .//reflect-metadata/Reflect.js
Critical dependencies:
841:28-35 require function is used in a way in which dependencies cannot be statically extracted
@ .//reflect-metadata/Reflect.js 841:28-35

WARNING in .//reflect-metadata/package.json
Module parse failed: C:\source\temp4\node_modules\reflect-metadata\package.json Unexpected token (2:9)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:9)
at Parser.pp$4.raise (C:\source\temp4\node_modules\acorn\dist\acorn.js:2221:15)
at Parser.pp.unexpected (C:\source\temp4\node_modules\acorn\dist\acorn.js:603:10)
at Parser.pp.semicolon (C:\source\temp4\node_modules\acorn\dist\acorn.js:581:61)
at Parser.pp$1.parseExpressionStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:966:10)
at Parser.pp$1.parseStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:730:24)
at Parser.pp$1.parseBlock (C:\source\temp4\node_modules\acorn\dist\acorn.js:981:25)
at Parser.pp$1.parseStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:709:33)
at Parser.pp$1.parseTopLevel (C:\source\temp4\node_modules\acorn\dist\acorn.js:638:25)
at Parser.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:516:17)
at Object.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:3098:39)
at Parser.parse (C:\source\temp4\node_modules\webpack\lib\Parser.js:902:15)
at DependenciesBlock. (C:\source\temp4\node_modules\webpack\lib\NormalModule.js:104:16)
at DependenciesBlock.onModuleBuild (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:310:10)
at nextLoader (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:275:25)
at C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:259:5
at Storage.provide (C:\source\temp4\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:52:20)
at CachedInputFileSystem.readFile (C:\source\temp4\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:140:24)
@ .//reflect-metadata ^./.*$

WARNING in .//reflect-metadata/README.md
Module parse failed: C:\source\temp4\node_modules\reflect-metadata\README.md Unexpected token (1:9)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (1:9)
at Parser.pp$4.raise (C:\source\temp4\node_modules\acorn\dist\acorn.js:2221:15)
at Parser.pp.unexpected (C:\source\temp4\node_modules\acorn\dist\acorn.js:603:10)
at Parser.pp.semicolon (C:\source\temp4\node_modules\acorn\dist\acorn.js:581:61)
at Parser.pp$1.parseExpressionStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:966:10)
at Parser.pp$1.parseStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:730:24)
at Parser.pp$1.parseTopLevel (C:\source\temp4\node_modules\acorn\dist\acorn.js:638:25)
at Parser.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:516:17)
at Object.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:3098:39)
at Parser.parse (C:\source\temp4\node_modules\webpack\lib\Parser.js:902:15)
at DependenciesBlock. (C:\source\temp4\node_modules\webpack\lib\NormalModule.js:104:16)
at DependenciesBlock.onModuleBuild (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:310:10)
at nextLoader (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:275:25)
at C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:259:5
at Storage.finished (C:\source\temp4\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:38:16)
at C:\source\temp4\node_modules\graceful-fs\graceful-fs.js:78:16
at FSReqWrap.readFileAfterClose as oncomplete
@ .//reflect-metadata ^./.*$

WARNING in .//reflect-metadata/Reflect.js.map
Module parse failed: C:\source\temp4\node_modules\reflect-metadata\Reflect.js.map Unexpected token (1:10)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (1:10)
at Parser.pp$4.raise (C:\source\temp4\node_modules\acorn\dist\acorn.js:2221:15)
at Parser.pp.unexpected (C:\source\temp4\node_modules\acorn\dist\acorn.js:603:10)
at Parser.pp.semicolon (C:\source\temp4\node_modules\acorn\dist\acorn.js:581:61)
at Parser.pp$1.parseExpressionStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:966:10)
at Parser.pp$1.parseStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:730:24)
at Parser.pp$1.parseBlock (C:\source\temp4\node_modules\acorn\dist\acorn.js:981:25)
at Parser.pp$1.parseStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:709:33)
at Parser.pp$1.parseTopLevel (C:\source\temp4\node_modules\acorn\dist\acorn.js:638:25)
at Parser.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:516:17)
at Object.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:3098:39)
at Parser.parse (C:\source\temp4\node_modules\webpack\lib\Parser.js:902:15)
at DependenciesBlock. (C:\source\temp4\node_modules\webpack\lib\NormalModule.js:104:16)
at DependenciesBlock.onModuleBuild (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:310:10)
at nextLoader (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:275:25)
at C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:259:5
at Storage.finished (C:\source\temp4\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:38:16)
@ .//reflect-metadata ^./.*$

WARNING in .//reflect-metadata/LICENSE
Module parse failed: C:\source\temp4\node_modules\reflect-metadata\LICENSE Unexpected token (1:7)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (1:7)
at Parser.pp$4.raise (C:\source\temp4\node_modules\acorn\dist\acorn.js:2221:15)
at Parser.pp.unexpected (C:\source\temp4\node_modules\acorn\dist\acorn.js:603:10)
at Parser.pp.semicolon (C:\source\temp4\node_modules\acorn\dist\acorn.js:581:61)
at Parser.pp$1.parseExpressionStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:966:10)
at Parser.pp$1.parseStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:730:24)
at Parser.pp$1.parseTopLevel (C:\source\temp4\node_modules\acorn\dist\acorn.js:638:25)
at Parser.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:516:17)
at Object.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:3098:39)
at Parser.parse (C:\source\temp4\node_modules\webpack\lib\Parser.js:902:15)
at DependenciesBlock. (C:\source\temp4\node_modules\webpack\lib\NormalModule.js:104:16)
at DependenciesBlock.onModuleBuild (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:310:10)
at nextLoader (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:275:25)
at C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:259:5
at Storage.finished (C:\source\temp4\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:38:16)
at C:\source\temp4\node_modules\graceful-fs\graceful-fs.js:78:16
at FSReqWrap.readFileAfterClose as oncomplete
@ .//reflect-metadata ^./.*$

WARNING in .//reflect-metadata/bower.json
Module parse failed: C:\source\temp4\node_modules\reflect-metadata\bower.json Unexpected token (2:8)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:8)
at Parser.pp$4.raise (C:\source\temp4\node_modules\acorn\dist\acorn.js:2221:15)
at Parser.pp.unexpected (C:\source\temp4\node_modules\acorn\dist\acorn.js:603:10)
at Parser.pp.semicolon (C:\source\temp4\node_modules\acorn\dist\acorn.js:581:61)
at Parser.pp$1.parseExpressionStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:966:10)
at Parser.pp$1.parseStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:730:24)
at Parser.pp$1.parseBlock (C:\source\temp4\node_modules\acorn\dist\acorn.js:981:25)
at Parser.pp$1.parseStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:709:33)
at Parser.pp$1.parseTopLevel (C:\source\temp4\node_modules\acorn\dist\acorn.js:638:25)
at Parser.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:516:17)
at Object.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:3098:39)
at Parser.parse (C:\source\temp4\node_modules\webpack\lib\Parser.js:902:15)
at DependenciesBlock. (C:\source\temp4\node_modules\webpack\lib\NormalModule.js:104:16)
at DependenciesBlock.onModuleBuild (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:310:10)
at nextLoader (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:275:25)
at C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:259:5
at Storage.finished (C:\source\temp4\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:38:16)
@ .//reflect-metadata ^./.*$

WARNING in .//reflect-metadata/spec/biblio.json
Module parse failed: C:\source\temp4\node_modules\reflect-metadata\spec\biblio.json Unexpected token (2:56)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:56)
at Parser.pp$4.raise (C:\source\temp4\node_modules\acorn\dist\acorn.js:2221:15)
at Parser.pp.unexpected (C:\source\temp4\node_modules\acorn\dist\acorn.js:603:10)
at Parser.pp.semicolon (C:\source\temp4\node_modules\acorn\dist\acorn.js:581:61)
at Parser.pp$1.parseExpressionStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:966:10)
at Parser.pp$1.parseStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:730:24)
at Parser.pp$1.parseBlock (C:\source\temp4\node_modules\acorn\dist\acorn.js:981:25)
at Parser.pp$1.parseStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:709:33)
at Parser.pp$1.parseTopLevel (C:\source\temp4\node_modules\acorn\dist\acorn.js:638:25)
at Parser.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:516:17)
at Object.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:3098:39)
at Parser.parse (C:\source\temp4\node_modules\webpack\lib\Parser.js:902:15)
at DependenciesBlock. (C:\source\temp4\node_modules\webpack\lib\NormalModule.js:104:16)
at DependenciesBlock.onModuleBuild (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:310:10)
at nextLoader (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:275:25)
at C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:259:5
at Storage.finished (C:\source\temp4\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:38:16)
@ .//reflect-metadata ^./.*$

WARNING in .//reflect-metadata/tsconfig.json
Module parse failed: C:\source\temp4\node_modules\reflect-metadata\tsconfig.json Unexpected token (2:19)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:19)
at Parser.pp$4.raise (C:\source\temp4\node_modules\acorn\dist\acorn.js:2221:15)
at Parser.pp.unexpected (C:\source\temp4\node_modules\acorn\dist\acorn.js:603:10)
at Parser.pp.semicolon (C:\source\temp4\node_modules\acorn\dist\acorn.js:581:61)
at Parser.pp$1.parseExpressionStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:966:10)
at Parser.pp$1.parseStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:730:24)
at Parser.pp$1.parseBlock (C:\source\temp4\node_modules\acorn\dist\acorn.js:981:25)
at Parser.pp$1.parseStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:709:33)
at Parser.pp$1.parseTopLevel (C:\source\temp4\node_modules\acorn\dist\acorn.js:638:25)
at Parser.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:516:17)
at Object.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:3098:39)
at Parser.parse (C:\source\temp4\node_modules\webpack\lib\Parser.js:902:15)
at DependenciesBlock. (C:\source\temp4\node_modules\webpack\lib\NormalModule.js:104:16)
at DependenciesBlock.onModuleBuild (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:310:10)
at nextLoader (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:275:25)
at C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:259:5
at Storage.finished (C:\source\temp4\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:38:16)
@ .//reflect-metadata ^./.*$

WARNING in .//reflect-metadata/test/tsconfig.json
Module parse failed: C:\source\temp4\node_modules\reflect-metadata\test\tsconfig.json Unexpected token (2:19)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected token (2:19)
at Parser.pp$4.raise (C:\source\temp4\node_modules\acorn\dist\acorn.js:2221:15)
at Parser.pp.unexpected (C:\source\temp4\node_modules\acorn\dist\acorn.js:603:10)
at Parser.pp.semicolon (C:\source\temp4\node_modules\acorn\dist\acorn.js:581:61)
at Parser.pp$1.parseExpressionStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:966:10)
at Parser.pp$1.parseStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:730:24)
at Parser.pp$1.parseBlock (C:\source\temp4\node_modules\acorn\dist\acorn.js:981:25)
at Parser.pp$1.parseStatement (C:\source\temp4\node_modules\acorn\dist\acorn.js:709:33)
at Parser.pp$1.parseTopLevel (C:\source\temp4\node_modules\acorn\dist\acorn.js:638:25)
at Parser.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:516:17)
at Object.parse (C:\source\temp4\node_modules\acorn\dist\acorn.js:3098:39)
at Parser.parse (C:\source\temp4\node_modules\webpack\lib\Parser.js:902:15)
at DependenciesBlock. (C:\source\temp4\node_modules\webpack\lib\NormalModule.js:104:16)
at DependenciesBlock.onModuleBuild (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:310:10)
at nextLoader (C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:275:25)
at C:\source\temp4\node_modules\webpack-core\lib\NormalModuleMixin.js:259:5
at Storage.finished (C:\source\temp4\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:38:16)
@ .//reflect-metadata ^./.*$

WARNING in .//reflect-metadata/reflect-metadata.d.ts
Module build failed: Error: Typescript emitted no output for C:\source\temp4\node_modules\reflect-metadata\reflect-metadata.d.ts
at Object.loader (C:\source\temp4\node_modules\ts-loader\index.js:456:15)
@ .//reflect-metadata ^./.*$

WARNING in .//reflect-metadata/Reflect.ts
Critical dependencies:
841:28-35 require function is used in a way in which dependencies cannot be statically extracted
@ .//reflect-metadata/Reflect.ts 841:28-35

WARNING in .//reflect-metadata/typings.d.ts
Module build failed: Error: Typescript emitted no output for C:\source\temp4\node_modules\reflect-metadata\typings.d.ts
at Object.loader (C:\source\temp4\node_modules\ts-loader\index.js:456:15)
@ .//reflect-metadata ^./.*$

WARNING in .//reflect-metadata/typings/node.d.ts
Module build failed: Error: Typescript emitted no output for C:\source\temp4\node_modules\reflect-metadata\typings\node.d.ts
at Object.loader (C:\source\temp4\node_modules\ts-loader\index.js:456:15)
@ .//reflect-metadata ^./.*$

ERROR in ./~/reflect-metadata/Reflect.ts
(96,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(133,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(174,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(255,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(298,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(335,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(376,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(401,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(433,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(469,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(494,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(526,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(562,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(587,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(619,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(655,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(680,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(712,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(748,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(772,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(803,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(838,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(862,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(893,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(928,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(953,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(985,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in ./~/reflect-metadata/Reflect.ts
(1021,21): error TS2384: Overload signatures must all be ambient or non-ambient.

ERROR in C:\source\temp4\typings\globals\node\index.d.ts
(2299,5): error TS2309: An export assignment cannot be used in a module with other exported elements.

ERROR in C:\source\temp4\tsconfig.json
error TS6059: File 'C:/source/temp4/node_modules/reflect-metadata/Reflect.ts' is not under 'rootDir' 'C:/source/temp4/src'. 'rootDir' is expected to contain all source files.

ERROR in C:\source\temp4\tsconfig.json
error TS6059: File 'C:/source/temp4/node_modules/reflect-metadata/test/harness.ts' is not under 'rootDir' 'C:/source/temp4/src'. 'rootDir' is expected to contain all source files.

ERROR in C:\source\temp4\tsconfig.json
error TS6059: File 'C:/source/temp4/node_modules/reflect-metadata/test/reflect/reflect-decorate.ts' is not under 'rootDir' 'C:/source/temp4/src'. 'rootDir' is expected to contain all source files.

ERROR in C:\source\temp4\tsconfig.json
error TS6059: File 'C:/source/temp4/node_modules/reflect-metadata/test/reflect/reflect-definemetadata.ts' is not under 'rootDir' 'C:/source/temp4/src'. 'rootDir' is expected to contain all source files.

ERROR in C:\source\temp4\tsconfig.json
error TS6059: File 'C:/source/temp4/node_modules/reflect-metadata/test/reflect/reflect-deletemetadata.ts' is not under 'rootDir' 'C:/source/temp4/src'. 'rootDir' is expected to contain all source files.

ERROR in C:\source\temp4\tsconfig.json
error TS6059: File 'C:/source/temp4/node_modules/reflect-metadata/test/reflect/reflect-getmetadata.ts' is not under 'rootDir' 'C:/source/temp4/src'. 'rootDir' is expected to contain all source files.

ERROR in C:\source\temp4\tsconfig.json
error TS6059: File 'C:/source/temp4/node_modules/reflect-metadata/test/reflect/reflect-getmetadatakeys.ts' is not under 'rootDir' 'C:/source/temp4/src'. 'rootDir' is expected to contain all source files.

ERROR in C:\source\temp4\tsconfig.json
error TS6059: File 'C:/source/temp4/node_modules/reflect-metadata/test/reflect/reflect-getownmetadata.ts' is not under 'rootDir' 'C:/source/temp4/src'. 'rootDir' is expected to contain all source files.

ERROR in C:\source\temp4\tsconfig.json
error TS6059: File 'C:/source/temp4/node_modules/reflect-metadata/test/reflect/reflect-getownmetadatakeys.ts' is not under 'rootDir' 'C:/source/temp4/src'. 'rootDir' is expected to contain all source files.

ERROR in C:\source\temp4\tsconfig.json
error TS6059: File 'C:/source/temp4/node_modules/reflect-metadata/test/reflect/reflect-hasmetadata.ts' is not under 'rootDir' 'C:/source/temp4/src'. 'rootDir' is expected to contain all source files.

ERROR in C:\source\temp4\tsconfig.json
error TS6059: File 'C:/source/temp4/node_modules/reflect-metadata/test/reflect/reflect-hasownmetadata.ts' is not under 'rootDir' 'C:/source/temp4/src'. 'rootDir' is expected to contain all source files.

ERROR in C:\source\temp4\tsconfig.json
error TS6059: File 'C:/source/temp4/node_modules/reflect-metadata/test/reflect/reflect-metadata.ts' is not under 'rootDir' 'C:/source/temp4/src'. 'rootDir' is expected to contain all source files.

ERROR in C:\source\temp4\tsconfig.json
error TS6059: File 'C:/source/temp4/node_modules/reflect-metadata/test/run.ts' is not under 'rootDir' 'C:/source/temp4/src'. 'rootDir' is expected to contain all source files.

ERROR in C:\source\temp4\tsconfig.json
error TS6059: File 'C:/source/temp4/node_modules/reflect-metadata/test/spec.ts' is not under 'rootDir' 'C:/source/temp4/src'. 'rootDir' is expected to contain all source files.

Couldn't select CSS framework, How to add 'ng-bootstrap'?

I couldn't select CSS framework using arrow keys, and eventually "none" was selected.
When i pressed down arrow key,nothing changes ,
it stopped at "None" and couldn't change the option.

Currently, project run without bootstarp..
Now, I want to add ng-bootstrap.
So, how to set project environment for support ng-bootstrap?

Migrate to Angular 2 RC5