How to install Jest on macOS Mojave
1
On a MacBook Pro (Mojave) I have installed Node (it works).
npm install --save-dev jest
runs without errors, BUT jest is still not available:
jest --version bash: jest: command not found
What is wrong?
node.js macos-mojave
edited Jan 15 at 17:10
JakeGould
31.3k1096138
asked Jan 15 at 17:02
Jean-Marie LabordeJean-Marie Laborde
61
add a comment |
1
On a MacBook Pro (Mojave) I have installed Node (it works).
npm install --save-dev jest
runs without errors, BUT jest is still not available:
jest --version bash: jest: command not found
What is wrong?
node.js macos-mojave
edited Jan 15 at 17:10
JakeGould
31.3k1096138
asked Jan 15 at 17:02
Jean-Marie LabordeJean-Marie Laborde
61
Just because the command is not found does not mean it is not installed. You may have to navigate to the location, add the location to your default path, or use a fully qualified path to the executable you intend to run.
– HackSlash
Jan 15 at 21:12
De-installing Node and re-installing everything "globally" (option -g) has solved the problem. Thanks for your valuable help.
– Jean-Marie Laborde
Jan 16 at 18:17
I'm so happy you were able to resolve the problem on your own. Please post the fix as an answer to your own question and then hit the green check mark to accept your answer and close this question. You get points and people will stop coming here trying to help you.
– HackSlash
Jan 16 at 18:59
add a comment |
1
1
1
On a MacBook Pro (Mojave) I have installed Node (it works).
npm install --save-dev jest
runs without errors, BUT jest is still not available:
jest --version bash: jest: command not found
What is wrong?
node.js macos-mojave
edited Jan 15 at 17:10
JakeGould
31.3k1096138
asked Jan 15 at 17:02
Jean-Marie LabordeJean-Marie Laborde
61
On a MacBook Pro (Mojave) I have installed Node (it works).
npm install --save-dev jest
runs without errors, BUT jest is still not available:
jest --version bash: jest: command not found
What is wrong?
node.js macos-mojave
node.js macos-mojave
edited Jan 15 at 17:10
JakeGould
31.3k1096138
asked Jan 15 at 17:02
Jean-Marie LabordeJean-Marie Laborde
61
edited Jan 15 at 17:10
JakeGould
31.3k1096138
asked Jan 15 at 17:02
Jean-Marie LabordeJean-Marie Laborde
61
edited Jan 15 at 17:10
JakeGould
31.3k1096138
edited Jan 15 at 17:10
JakeGould
31.3k1096138
edited Jan 15 at 17:10
JakeGould
31.3k1096138
31.3k1096138
asked Jan 15 at 17:02
Jean-Marie LabordeJean-Marie Laborde
61
asked Jan 15 at 17:02
Jean-Marie LabordeJean-Marie Laborde
61
asked Jan 15 at 17:02
Jean-Marie LabordeJean-Marie Laborde
61
61
Just because the command is not found does not mean it is not installed. You may have to navigate to the location, add the location to your default path, or use a fully qualified path to the executable you intend to run.
– HackSlash
Jan 15 at 21:12
De-installing Node and re-installing everything "globally" (option -g) has solved the problem. Thanks for your valuable help.
– Jean-Marie Laborde
Jan 16 at 18:17
I'm so happy you were able to resolve the problem on your own. Please post the fix as an answer to your own question and then hit the green check mark to accept your answer and close this question. You get points and people will stop coming here trying to help you.
– HackSlash
Jan 16 at 18:59
add a comment |
Just because the command is not found does not mean it is not installed. You may have to navigate to the location, add the location to your default path, or use a fully qualified path to the executable you intend to run.
– HackSlash
Jan 15 at 21:12
De-installing Node and re-installing everything "globally" (option -g) has solved the problem. Thanks for your valuable help.
– Jean-Marie Laborde
Jan 16 at 18:17
I'm so happy you were able to resolve the problem on your own. Please post the fix as an answer to your own question and then hit the green check mark to accept your answer and close this question. You get points and people will stop coming here trying to help you.
– HackSlash
Jan 16 at 18:59
Just because the command is not found does not mean it is not installed. You may have to navigate to the location, add the location to your default path, or use a fully qualified path to the executable you intend to run.
– HackSlash
Jan 15 at 21:12
Just because the command is not found does not mean it is not installed. You may have to navigate to the location, add the location to your default path, or use a fully qualified path to the executable you intend to run.
– HackSlash
Jan 15 at 21:12
De-installing Node and re-installing everything "globally" (option -g) has solved the problem. Thanks for your valuable help.
– Jean-Marie Laborde
Jan 16 at 18:17
De-installing Node and re-installing everything "globally" (option -g) has solved the problem. Thanks for your valuable help.
– Jean-Marie Laborde
Jan 16 at 18:17
I'm so happy you were able to resolve the problem on your own. Please post the fix as an answer to your own question and then hit the green check mark to accept your answer and close this question. You get points and people will stop coming here trying to help you.
– HackSlash
Jan 16 at 18:59
I'm so happy you were able to resolve the problem on your own. Please post the fix as an answer to your own question and then hit the green check mark to accept your answer and close this question. You get points and people will stop coming here trying to help you.
– HackSlash
Jan 16 at 18:59
add a comment |
0
active
oldest
votes
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
});
}
});
draft saved
draft discarded
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%2f1394610%2fhow-to-install-jest-on-macos-mojave%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f1394610%2fhow-to-install-jest-on-macos-mojave%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
Just because the command is not found does not mean it is not installed. You may have to navigate to the location, add the location to your default path, or use a fully qualified path to the executable you intend to run.
– HackSlash
Jan 15 at 21:12
De-installing Node and re-installing everything "globally" (option -g) has solved the problem. Thanks for your valuable help.
– Jean-Marie Laborde
Jan 16 at 18:17
I'm so happy you were able to resolve the problem on your own. Please post the fix as an answer to your own question and then hit the green check mark to accept your answer and close this question. You get points and people will stop coming here trying to help you.
– HackSlash
Jan 16 at 18:59