Angular2 TodoMVC project doesn't load

[szaske]

Angular2 TodoMVC project stuck on 'Loading...'

I attempted to use your online tool at http://fountainjs.io/download/

Selected:
Angular2
Webpack/NPM
Typescript
Sass
TodoMVC

It would be nice if you included a README file with the download, but without one I just ran npm install and then gulp serve
ran into a known issue with gulp so I did as you suggested and ran npm run serve instead and ran into this problem. The app just got stuck at 'loading...'

Error Message & Stack Trace

No errors in the console, the project just stuck at 'loading...'

Config

Here is my .yo-rc.json file.

{
  "generator-fountain-angular2": {
    "version": "1.0.0",
    "props": {
      "skipInstall": true,
      "framework": "angular2",
      "modules": "webpack",
      "js": "typescript",
      "ci": "",
      "css": "scss",
      "resolved": "/Users/swiip/Workspace/FountainJS/fountain/generator-fountain-angular2/generators/app/index.js",
      "namespace": "fountain-angular2:app",
      "_": [],
      "sample": "todoMVC",
      "router": "router"
    }
  }
}

Relevant Links

A link to the resulting project can be found on github here

Environment

Node.js v8.2.1
darwin 15.6.0
yo not installed, but I don't think it's needed
npm 5.3.0

[szaske]

I found a work around. Apparently I need to run using Typescript 2.3.4. Once I changed to that, it started working.

[angeagu]

Hello,

I ran into a similar problem, I built a project using Yeoman generator with:
Angular2
SystemJS
Typescript
Sass
TodoMVC or HelloWorld landing page

And application just stucks on 'Loading...'
Even browser tab seems to hang, avoiding browser to close.
Tried with both gulp serve and npm run serve and same issue. Checked
gulp task doesn't reload the changes in index.html files. I have to Ctrl+Save
the file to reloadBrowserSync task to be executed, but even with this, application
is still hanged.
Even I tried the workaround proposed by @szaske and installed Typescript 2.3.4 but still no luck.
I'm using Mac, with webstorm 2017, npm 5.6.0 and node-nvm 8.10.0

Did you find any solution or workaround on this?