DanWahlin / Angular-JumpStart

Angular and TypeScript JumpStart example application

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Not able to build the project

mayurbombale opened this issue · comments

Hi DanWahlin,

When i try to build project using cmd ng build --watch.Its giving me error

Your global Angular CLI version (6.1.4) is greater than your local
version (6.0.5). The local Angular CLI version is used.

src/app/customer/customer-details.component.sandbox.ts(1,27): error TS2307: Cannot find module 'angular-playground'. Cannot find module 'angular-playground'.

So, when i install playground using cmd npm run playground its giving me error as below :

at startup (internal/bootstrap/node.js:201:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:516:3)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! angular-jump-start@0.0.0 playground: angular-playground
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the angular-jump-start@0.0.0 playground script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\710987\AppData\Roaming\npm-cache_logs\2018-08-23T14_18_43_263Z-debug.log

Please help me.

That's a warning actually, not an error for the CLI. It just means your version of the global Angular CLI install is greater than the project version. You don't need to do anything to install playground. Just follow the steps in the readme and run the npm install - that grabs the playground for you. It looks like you didn't run npm install or it didn't run successfully.

It all works correctly (have 24 people in a class this week using this project), so if you get a problem there, try deleting node_modules and re-running npm install. Make sure to go through all of the steps listed in the readme.

Hi DanWahlin,

Thanks for your reply

When i run cmd npm install its giving me some error.As i am new to angular please help me.

C:\Users\710987\Downloads\Angular-JumpStart-master>cd Angular-JumpStart-master

C:\Users\710987\Downloads\Angular-JumpStart-master\Angular-JumpStart-master>npm
install

puppeteer@1.4.0 install C:\Users\710987\Downloads\Angular-JumpStart-master\Ang
ular-JumpStart-master\node_modules\puppeteer
node install.js

ERROR: Failed to download Chromium r555668! Set "PUPPETEER_SKIP_CHROMIUM_DOWNLOA
D" env variable to skip download.
{ Error: connect ECONNREFUSED 172.217.166.176:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1174:14)
errno: 'ECONNREFUSED',
code: 'ECONNREFUSED',
syscall: 'connect',
address: '172.217.166.176',
port: 443 }
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules\fse
vents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@
1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}
)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! puppeteer@1.4.0 install: node install.js
npm ERR! Exit status 1

Hi DanWahlin,

When i run project using cmd npm start,its giving me below error

C:\Users\710987\Downloads\Angular-JumpStart-master\Angular-JumpStart-master>npm start

angular-jump-start@0.0.0 start C:\Users\710987\Downloads\Angular-JumpStart-master\Angular-JumpStart-maste
r
node server.js

Express listening on port 3000.
Browser closed.
Error: ENOENT: no such file or directory, stat 'C:\Users\710987\Downloads\Angular-JumpStart-master\Angular-
JumpStart-master\dist\index.html'
Error: ENOENT: no such file or directory, stat 'C:\Users\710987\Downloads\Angular-JumpStart-master\Angular-
JumpStart-master\dist\index.html'
Error: ENOENT: no such file or directory, stat 'C:\Users\710987\Downloads\Angular-JumpStart-master\Angular-
JumpStart-master\dist\index.html'

For the 2nd message, it looks like your machine is refusing to do a download or the service called is refusing.... I'm not sure which (ECONNREFUSED). I won't be able to help with that one since it could be a variety of issues causing it such as a proxy server or something else on your network refusing to access a resource. That's an npm access issue I'm guessing.

For the next one, make sure the ng build is complete before running npm start. Make sure you've run all the steps in the readme in the order listed.

Hi DanWahlin,

Thanks for your quick response.I will try doing it on some another machine.