During installing express package in Node js, I got an error
I have installed nodejs version node-v8.12.0-x64.msi.
I am installing express using npm install express --save in windows but getting following error
And also an important update only express is the package that causes problem otherwise other packages are installing properly. I also installed previous versions but still no luck.
Any suggestions would be gently appreciated.
node.js npm
edited Nov 13 '18 at 12:19
Yannick Loriot
6,16522550
asked Nov 13 '18 at 11:35
R.CR.C
12
add a comment |
I have installed nodejs version node-v8.12.0-x64.msi.
I am installing express using npm install express --save in windows but getting following error
And also an important update only express is the package that causes problem otherwise other packages are installing properly. I also installed previous versions but still no luck.
Any suggestions would be gently appreciated.
node.js npm
edited Nov 13 '18 at 12:19
Yannick Loriot
6,16522550
asked Nov 13 '18 at 11:35
R.CR.C
12
add a comment |
I have installed nodejs version node-v8.12.0-x64.msi.
I am installing express using npm install express --save in windows but getting following error
And also an important update only express is the package that causes problem otherwise other packages are installing properly. I also installed previous versions but still no luck.
Any suggestions would be gently appreciated.
node.js npm
edited Nov 13 '18 at 12:19
Yannick Loriot
6,16522550
asked Nov 13 '18 at 11:35
R.CR.C
12
I have installed nodejs version node-v8.12.0-x64.msi.
I am installing express using npm install express --save in windows but getting following error
And also an important update only express is the package that causes problem otherwise other packages are installing properly. I also installed previous versions but still no luck.
Any suggestions would be gently appreciated.
node.js npm
node.js npm
edited Nov 13 '18 at 12:19
Yannick Loriot
6,16522550
asked Nov 13 '18 at 11:35
R.CR.C
12
edited Nov 13 '18 at 12:19
Yannick Loriot
6,16522550
asked Nov 13 '18 at 11:35
R.CR.C
12
edited Nov 13 '18 at 12:19
Yannick Loriot
6,16522550
edited Nov 13 '18 at 12:19
Yannick Loriot
6,16522550
edited Nov 13 '18 at 12:19
Yannick Loriot
6,16522550
6,16522550
asked Nov 13 '18 at 11:35
R.CR.C
12
asked Nov 13 '18 at 11:35
R.CR.C
12
asked Nov 13 '18 at 11:35
R.CR.C
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Your problem is probably in your package.json or package-lock.json files. You should include de content in the **-debug.log file to further info, try to create a new folder an then use "npm init", press enter for all questions then install Express.js. If all works the problem is in those files.
answered Nov 13 '18 at 11:47
desoaresdesoares
681512
Hi desoares, I tried everything to run express, including also tried different versions of node. But still problem stands. And also I create a new folder and use "npm init" and after that installed express but same problem occur. So what can I do next?
– R.C
Nov 14 '18 at 11:13
Post the content of the latest **-debug.log for further info. The second to last line of the print screen has the path.
– desoares
Nov 14 '18 at 11:55
I cannot understood yet, What is the problem, In the logs it show same thing that I got in terminal. So what is the best possible solution?
– R.C
Nov 15 '18 at 5:07
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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%2fstackoverflow.com%2fquestions%2f53280163%2fduring-installing-express-package-in-node-js-i-got-an-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
Your problem is probably in your package.json or package-lock.json files. You should include de content in the **-debug.log file to further info, try to create a new folder an then use "npm init", press enter for all questions then install Express.js. If all works the problem is in those files.
answered Nov 13 '18 at 11:47
desoaresdesoares
681512
Hi desoares, I tried everything to run express, including also tried different versions of node. But still problem stands. And also I create a new folder and use "npm init" and after that installed express but same problem occur. So what can I do next?
– R.C
Nov 14 '18 at 11:13
Post the content of the latest **-debug.log for further info. The second to last line of the print screen has the path.
– desoares
Nov 14 '18 at 11:55
I cannot understood yet, What is the problem, In the logs it show same thing that I got in terminal. So what is the best possible solution?
– R.C
Nov 15 '18 at 5:07
add a comment |
Your problem is probably in your package.json or package-lock.json files. You should include de content in the **-debug.log file to further info, try to create a new folder an then use "npm init", press enter for all questions then install Express.js. If all works the problem is in those files.
answered Nov 13 '18 at 11:47
desoaresdesoares
681512
Hi desoares, I tried everything to run express, including also tried different versions of node. But still problem stands. And also I create a new folder and use "npm init" and after that installed express but same problem occur. So what can I do next?
– R.C
Nov 14 '18 at 11:13
Post the content of the latest **-debug.log for further info. The second to last line of the print screen has the path.
– desoares
Nov 14 '18 at 11:55
I cannot understood yet, What is the problem, In the logs it show same thing that I got in terminal. So what is the best possible solution?
– R.C
Nov 15 '18 at 5:07
add a comment |
Your problem is probably in your package.json or package-lock.json files. You should include de content in the **-debug.log file to further info, try to create a new folder an then use "npm init", press enter for all questions then install Express.js. If all works the problem is in those files.
answered Nov 13 '18 at 11:47
desoaresdesoares
681512
Your problem is probably in your package.json or package-lock.json files. You should include de content in the **-debug.log file to further info, try to create a new folder an then use "npm init", press enter for all questions then install Express.js. If all works the problem is in those files.
answered Nov 13 '18 at 11:47
desoaresdesoares
681512
answered Nov 13 '18 at 11:47
desoaresdesoares
681512
answered Nov 13 '18 at 11:47
desoaresdesoares
681512
answered Nov 13 '18 at 11:47
desoaresdesoares
681512
681512
Hi desoares, I tried everything to run express, including also tried different versions of node. But still problem stands. And also I create a new folder and use "npm init" and after that installed express but same problem occur. So what can I do next?
– R.C
Nov 14 '18 at 11:13
Post the content of the latest **-debug.log for further info. The second to last line of the print screen has the path.
– desoares
Nov 14 '18 at 11:55
I cannot understood yet, What is the problem, In the logs it show same thing that I got in terminal. So what is the best possible solution?
– R.C
Nov 15 '18 at 5:07
add a comment |
Hi desoares, I tried everything to run express, including also tried different versions of node. But still problem stands. And also I create a new folder and use "npm init" and after that installed express but same problem occur. So what can I do next?
– R.C
Nov 14 '18 at 11:13
Post the content of the latest **-debug.log for further info. The second to last line of the print screen has the path.
– desoares
Nov 14 '18 at 11:55
I cannot understood yet, What is the problem, In the logs it show same thing that I got in terminal. So what is the best possible solution?
– R.C
Nov 15 '18 at 5:07
Hi desoares, I tried everything to run express, including also tried different versions of node. But still problem stands. And also I create a new folder and use "npm init" and after that installed express but same problem occur. So what can I do next?
– R.C
Nov 14 '18 at 11:13
Hi desoares, I tried everything to run express, including also tried different versions of node. But still problem stands. And also I create a new folder and use "npm init" and after that installed express but same problem occur. So what can I do next?
– R.C
Nov 14 '18 at 11:13
Post the content of the latest **-debug.log for further info. The second to last line of the print screen has the path.
– desoares
Nov 14 '18 at 11:55
Post the content of the latest **-debug.log for further info. The second to last line of the print screen has the path.
– desoares
Nov 14 '18 at 11:55
I cannot understood yet, What is the problem, In the logs it show same thing that I got in terminal. So what is the best possible solution?
– R.C
Nov 15 '18 at 5:07
I cannot understood yet, What is the problem, In the logs it show same thing that I got in terminal. So what is the best possible solution?
– R.C
Nov 15 '18 at 5:07
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53280163%2fduring-installing-express-package-in-node-js-i-got-an-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
