Angular CLI error
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am having an issue while installing Angular CLI.
I wrote a command on cmd prompt on Windows 10:
npm install -g @angular/cli
The following error occurred:
Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning ETIMEDOUT: request to https://registry.npmjs.org/@angular%2fcli failed, reason: connect ETIMEDOUT 104.16.25.35:443
Here is a picture of the situation:
javascript node.js
edited Jan 27 at 21:58
zx485
1,3721914
asked Jan 27 at 21:23
Abdul MutaalAbdul Mutaal
63
add a comment |
I am having an issue while installing Angular CLI.
I wrote a command on cmd prompt on Windows 10:
npm install -g @angular/cli
The following error occurred:
Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning ETIMEDOUT: request to https://registry.npmjs.org/@angular%2fcli failed, reason: connect ETIMEDOUT 104.16.25.35:443
Here is a picture of the situation:
javascript node.js
edited Jan 27 at 21:58
zx485
1,3721914
asked Jan 27 at 21:23
Abdul MutaalAbdul Mutaal
63
Trynpm cache clear --force. If that doesn't work, try removing thepackage.json.lockfile, verify your npm cache withnpm cache verifyand then try to install angular again.
– DrZoo
Jan 28 at 6:15
Thankyou DrZoo....this worked
– Abdul Mutaal
Jan 28 at 15:15
You're welcome. Which one made it work? Just doing thenpm cache clear --forceor did you have to remove the.lockfile and verify the cache again?
– DrZoo
Jan 28 at 15:17
DrZoo ...Just npm cache clear --force
– Abdul Mutaal
Jan 28 at 15:18
add a comment |
I am having an issue while installing Angular CLI.
I wrote a command on cmd prompt on Windows 10:
npm install -g @angular/cli
The following error occurred:
Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning ETIMEDOUT: request to https://registry.npmjs.org/@angular%2fcli failed, reason: connect ETIMEDOUT 104.16.25.35:443
Here is a picture of the situation:
javascript node.js
edited Jan 27 at 21:58
zx485
1,3721914
asked Jan 27 at 21:23
Abdul MutaalAbdul Mutaal
63
I am having an issue while installing Angular CLI.
I wrote a command on cmd prompt on Windows 10:
npm install -g @angular/cli
The following error occurred:
Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning ETIMEDOUT: request to https://registry.npmjs.org/@angular%2fcli failed, reason: connect ETIMEDOUT 104.16.25.35:443
Here is a picture of the situation:
javascript node.js
javascript node.js
edited Jan 27 at 21:58
zx485
1,3721914
asked Jan 27 at 21:23
Abdul MutaalAbdul Mutaal
63
edited Jan 27 at 21:58
zx485
1,3721914
asked Jan 27 at 21:23
Abdul MutaalAbdul Mutaal
63
edited Jan 27 at 21:58
zx485
1,3721914
edited Jan 27 at 21:58
zx485
1,3721914
edited Jan 27 at 21:58
zx485
1,3721914
1,3721914
asked Jan 27 at 21:23
Abdul MutaalAbdul Mutaal
63
asked Jan 27 at 21:23
Abdul MutaalAbdul Mutaal
63
asked Jan 27 at 21:23
Abdul MutaalAbdul Mutaal
63
63
Trynpm cache clear --force. If that doesn't work, try removing thepackage.json.lockfile, verify your npm cache withnpm cache verifyand then try to install angular again.
– DrZoo
Jan 28 at 6:15
Thankyou DrZoo....this worked
– Abdul Mutaal
Jan 28 at 15:15
You're welcome. Which one made it work? Just doing thenpm cache clear --forceor did you have to remove the.lockfile and verify the cache again?
– DrZoo
Jan 28 at 15:17
DrZoo ...Just npm cache clear --force
– Abdul Mutaal
Jan 28 at 15:18
add a comment |
Trynpm cache clear --force. If that doesn't work, try removing thepackage.json.lockfile, verify your npm cache withnpm cache verifyand then try to install angular again.
– DrZoo
Jan 28 at 6:15
Thankyou DrZoo....this worked
– Abdul Mutaal
Jan 28 at 15:15
You're welcome. Which one made it work? Just doing thenpm cache clear --forceor did you have to remove the.lockfile and verify the cache again?
– DrZoo
Jan 28 at 15:17
DrZoo ...Just npm cache clear --force
– Abdul Mutaal
Jan 28 at 15:18
Try
npm cache clear --force. If that doesn't work, try removing the package.json.lock file, verify your npm cache with npm cache verify and then try to install angular again.– DrZoo
Jan 28 at 6:15
Try
npm cache clear --force. If that doesn't work, try removing the package.json.lock file, verify your npm cache with npm cache verify and then try to install angular again.– DrZoo
Jan 28 at 6:15
Thankyou DrZoo....this worked
– Abdul Mutaal
Jan 28 at 15:15
Thankyou DrZoo....this worked
– Abdul Mutaal
Jan 28 at 15:15
You're welcome. Which one made it work? Just doing the
npm cache clear --force or did you have to remove the .lock file and verify the cache again?– DrZoo
Jan 28 at 15:17
You're welcome. Which one made it work? Just doing the
npm cache clear --force or did you have to remove the .lock file and verify the cache again?– DrZoo
Jan 28 at 15:17
DrZoo ...Just npm cache clear --force
– Abdul Mutaal
Jan 28 at 15:18
DrZoo ...Just npm cache clear --force
– Abdul Mutaal
Jan 28 at 15:18
add a comment |
1 Answer
1
active
oldest
votes
Running the command npm cache clear --force will usually solve this problem.
If npm cache clear --force does not solve the problem, you can try removing the package.json.lock file from your project, and then verify the npm cache again with the command npm cache verify.
answered Jan 28 at 15:22
DrZooDrZoo
6,10821842
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1399038%2fangular-cli-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Running the command npm cache clear --force will usually solve this problem.
If npm cache clear --force does not solve the problem, you can try removing the package.json.lock file from your project, and then verify the npm cache again with the command npm cache verify.
answered Jan 28 at 15:22
DrZooDrZoo
6,10821842
add a comment |
Running the command npm cache clear --force will usually solve this problem.
If npm cache clear --force does not solve the problem, you can try removing the package.json.lock file from your project, and then verify the npm cache again with the command npm cache verify.
answered Jan 28 at 15:22
DrZooDrZoo
6,10821842
add a comment |
Running the command npm cache clear --force will usually solve this problem.
If npm cache clear --force does not solve the problem, you can try removing the package.json.lock file from your project, and then verify the npm cache again with the command npm cache verify.
answered Jan 28 at 15:22
DrZooDrZoo
6,10821842
Running the command npm cache clear --force will usually solve this problem.
If npm cache clear --force does not solve the problem, you can try removing the package.json.lock file from your project, and then verify the npm cache again with the command npm cache verify.
answered Jan 28 at 15:22
DrZooDrZoo
6,10821842
answered Jan 28 at 15:22
DrZooDrZoo
6,10821842
answered Jan 28 at 15:22
DrZooDrZoo
6,10821842
answered Jan 28 at 15:22
DrZooDrZoo
6,10821842
6,10821842
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1399038%2fangular-cli-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Try
npm cache clear --force. If that doesn't work, try removing thepackage.json.lockfile, verify your npm cache withnpm cache verifyand then try to install angular again.– DrZoo
Jan 28 at 6:15
Thankyou DrZoo....this worked
– Abdul Mutaal
Jan 28 at 15:15
You're welcome. Which one made it work? Just doing the
npm cache clear --forceor did you have to remove the.lockfile and verify the cache again?– DrZoo
Jan 28 at 15:17
DrZoo ...Just npm cache clear --force
– Abdul Mutaal
Jan 28 at 15:18