nvm with yarn Yarn requires Node.js 4.0 or higher to be installed
2
I have nvm:
nvm ls
v8.11.3
v8.11.4
-> v11.1.0
default -> 8.11.4 (-> v8.11.4)
node -> stable (-> v11.1.0) (default)
stable -> 11.1 (-> v11.1.0) (default)
I installed yarn with:
sudo apt-get install --no-install-recommends yarn
I also added in .bashrc alias node=nodejs. But when I try yarn install I see:
Yarn requires Node.js 4.0 or higher to be installed.
How can I fix it?
yarnpkg nvm
edited Nov 12 '18 at 17:25
tk421
3,37131426
asked Nov 12 '18 at 16:15
allay
137
add a comment |
2
I have nvm:
nvm ls
v8.11.3
v8.11.4
-> v11.1.0
default -> 8.11.4 (-> v8.11.4)
node -> stable (-> v11.1.0) (default)
stable -> 11.1 (-> v11.1.0) (default)
I installed yarn with:
sudo apt-get install --no-install-recommends yarn
I also added in .bashrc alias node=nodejs. But when I try yarn install I see:
Yarn requires Node.js 4.0 or higher to be installed.
How can I fix it?
yarnpkg nvm
edited Nov 12 '18 at 17:25
tk421
3,37131426
asked Nov 12 '18 at 16:15
allay
137
add a comment |
2
2
2
0
I have nvm:
nvm ls
v8.11.3
v8.11.4
-> v11.1.0
default -> 8.11.4 (-> v8.11.4)
node -> stable (-> v11.1.0) (default)
stable -> 11.1 (-> v11.1.0) (default)
I installed yarn with:
sudo apt-get install --no-install-recommends yarn
I also added in .bashrc alias node=nodejs. But when I try yarn install I see:
Yarn requires Node.js 4.0 or higher to be installed.
How can I fix it?
yarnpkg nvm
edited Nov 12 '18 at 17:25
tk421
3,37131426
asked Nov 12 '18 at 16:15
allay
137
I have nvm:
nvm ls
v8.11.3
v8.11.4
-> v11.1.0
default -> 8.11.4 (-> v8.11.4)
node -> stable (-> v11.1.0) (default)
stable -> 11.1 (-> v11.1.0) (default)
I installed yarn with:
sudo apt-get install --no-install-recommends yarn
I also added in .bashrc alias node=nodejs. But when I try yarn install I see:
Yarn requires Node.js 4.0 or higher to be installed.
How can I fix it?
yarnpkg nvm
yarnpkg nvm
edited Nov 12 '18 at 17:25
tk421
3,37131426
asked Nov 12 '18 at 16:15
allay
137
edited Nov 12 '18 at 17:25
tk421
3,37131426
asked Nov 12 '18 at 16:15
allay
137
edited Nov 12 '18 at 17:25
tk421
3,37131426
edited Nov 12 '18 at 17:25
tk421
3,37131426
edited Nov 12 '18 at 17:25
tk421
3,37131426
3,37131426
asked Nov 12 '18 at 16:15
allay
137
asked Nov 12 '18 at 16:15
allay
137
asked Nov 12 '18 at 16:15
allay
137
137
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
0
This gist helped on this problem.
Run the following commands
echo "==> Installing Yarn package manager"
rm -rf ~/.yarn
curl -o- -L https://yarnpkg.com/install.sh | bash
# Yarn configurations
export PATH="$HOME/.yarn/bin:$PATH"
yarn config set prefix ~/.yarn -g
And add the following in ~/.bashrc
export PATH="$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH"
It should then work properly without the warning after restarting the shell.
answered Nov 23 '18 at 6:09
Toilal
2,2971727
1
ty for answer. I try to do this steps when i search in google my problem. The solution was simple: the problem was not in my development environment, but in the line of code that my partner added to webpack.config "preinstall": "sudo yarn global add prettifier eslint flow-bin" (he says it needed on macOS, i use Ubuntu)
– allay
Nov 27 '18 at 13:19
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
});
}
});
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%2fstackoverflow.com%2fquestions%2f53266097%2fnvm-with-yarn-yarn-requires-node-js-4-0-or-higher-to-be-installed%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
0
This gist helped on this problem.
Run the following commands
echo "==> Installing Yarn package manager"
rm -rf ~/.yarn
curl -o- -L https://yarnpkg.com/install.sh | bash
# Yarn configurations
export PATH="$HOME/.yarn/bin:$PATH"
yarn config set prefix ~/.yarn -g
And add the following in ~/.bashrc
export PATH="$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH"
It should then work properly without the warning after restarting the shell.
answered Nov 23 '18 at 6:09
Toilal
2,2971727
1
ty for answer. I try to do this steps when i search in google my problem. The solution was simple: the problem was not in my development environment, but in the line of code that my partner added to webpack.config "preinstall": "sudo yarn global add prettifier eslint flow-bin" (he says it needed on macOS, i use Ubuntu)
– allay
Nov 27 '18 at 13:19
add a comment |
0
This gist helped on this problem.
Run the following commands
echo "==> Installing Yarn package manager"
rm -rf ~/.yarn
curl -o- -L https://yarnpkg.com/install.sh | bash
# Yarn configurations
export PATH="$HOME/.yarn/bin:$PATH"
yarn config set prefix ~/.yarn -g
And add the following in ~/.bashrc
export PATH="$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH"
It should then work properly without the warning after restarting the shell.
answered Nov 23 '18 at 6:09
Toilal
2,2971727
1
ty for answer. I try to do this steps when i search in google my problem. The solution was simple: the problem was not in my development environment, but in the line of code that my partner added to webpack.config "preinstall": "sudo yarn global add prettifier eslint flow-bin" (he says it needed on macOS, i use Ubuntu)
– allay
Nov 27 '18 at 13:19
add a comment |
0
0
0
This gist helped on this problem.
Run the following commands
echo "==> Installing Yarn package manager"
rm -rf ~/.yarn
curl -o- -L https://yarnpkg.com/install.sh | bash
# Yarn configurations
export PATH="$HOME/.yarn/bin:$PATH"
yarn config set prefix ~/.yarn -g
And add the following in ~/.bashrc
export PATH="$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH"
It should then work properly without the warning after restarting the shell.
answered Nov 23 '18 at 6:09
Toilal
2,2971727
This gist helped on this problem.
Run the following commands
echo "==> Installing Yarn package manager"
rm -rf ~/.yarn
curl -o- -L https://yarnpkg.com/install.sh | bash
# Yarn configurations
export PATH="$HOME/.yarn/bin:$PATH"
yarn config set prefix ~/.yarn -g
And add the following in ~/.bashrc
export PATH="$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH"
It should then work properly without the warning after restarting the shell.
answered Nov 23 '18 at 6:09
Toilal
2,2971727
answered Nov 23 '18 at 6:09
Toilal
2,2971727
answered Nov 23 '18 at 6:09
Toilal
2,2971727
answered Nov 23 '18 at 6:09
Toilal
2,2971727
2,2971727
1
ty for answer. I try to do this steps when i search in google my problem. The solution was simple: the problem was not in my development environment, but in the line of code that my partner added to webpack.config "preinstall": "sudo yarn global add prettifier eslint flow-bin" (he says it needed on macOS, i use Ubuntu)
– allay
Nov 27 '18 at 13:19
add a comment |
1
ty for answer. I try to do this steps when i search in google my problem. The solution was simple: the problem was not in my development environment, but in the line of code that my partner added to webpack.config "preinstall": "sudo yarn global add prettifier eslint flow-bin" (he says it needed on macOS, i use Ubuntu)
– allay
Nov 27 '18 at 13:19
1
1
ty for answer. I try to do this steps when i search in google my problem. The solution was simple: the problem was not in my development environment, but in the line of code that my partner added to webpack.config "preinstall": "sudo yarn global add prettifier eslint flow-bin" (he says it needed on macOS, i use Ubuntu)
– allay
Nov 27 '18 at 13:19
ty for answer. I try to do this steps when i search in google my problem. The solution was simple: the problem was not in my development environment, but in the line of code that my partner added to webpack.config "preinstall": "sudo yarn global add prettifier eslint flow-bin" (he says it needed on macOS, i use Ubuntu)
– allay
Nov 27 '18 at 13:19
add a comment |
draft saved
draft discarded
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2fstackoverflow.com%2fquestions%2f53266097%2fnvm-with-yarn-yarn-requires-node-js-4-0-or-higher-to-be-installed%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
