unable to start about ani-angular-2 HOT 6 CLOSED

Before doing following step just re clone the project and try
OR
try following steps:
1: MSBuild Tool 2013 use https://www.microsoft.com/en-in/download/confirmation.aspx?id=40760
2: ts-node installed globally npm install -g ts-node
3: Run the Command Prompt with administrator privileges.
4: npm install —msvs_version=2013
5: npm start

from ani-angular-2.

Is there any error in npm install?

from ani-angular-2.

no

On Mon, Sep 26, 2016 at 8:27 AM, Nitin Kumar Mishra <
[email protected]> wrote:

Is there any error in npm install?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#7 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARazpG4SoR2jLBwO2z-TzLEpBkcpst2Zks5qt1fSgaJpZM4KGBcp
.

from ani-angular-2.

in my case I had to install gulp and highchart globally using admin privileges on windows and import into the project,afterwards,npm start worked :Below are the steps,using admin priveleges
1.npm install -g gulp 2.npm install -g highchart 3.Now cd into the root of ani-angular-2. 4.npm install gulp --save 5.npm install highchart --save 6.npm start
This worked for me.

from ani-angular-2.

Thanks a lot

On Oct 1, 2016 13:27, "AcePRbk" [email protected] wrote:

in my case I had to install gulp and highchart globally using admin
privileges on windows and import into the project,afterwards,npm start
worked :Below are the steps,using admin priveleges
1.npm install -g gulp
2.npm install -g highchart
3.Now cd into the root of ani-angular-2.
4.npm install gulp --save
5.npm install highchart --save
6.npm start
This worked for me.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#7 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARazpCOTJumTA6hkVreAZ6VgD7f0kKFwks5qvjWggaJpZM4KGBcp
.

from ani-angular-2.

how to resolve this issue, when i was run serve.prod

Failed at the [email protected] serve.prod script.

This is probably not a problem with npm. There is likely additional logging output above.

node ---v6.12.0
npm ---5.5.1

from ani-angular-2.