Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (57)
I am getting the error:
Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (57)
while running gulp command.
I have tried deleting node_modules folder and re-running npm install after running npm cache clean. I have tried the highly recommended npm rebuild node-sass. But, to no avail.
Version information:
- UBUNTU: 18.04.1
- node: 5.4.0
- npm: 3.3.12
- node-sass:
- gulp-sass@2.3.2
- node-sass@3.13.1
- gulp-sass@2.3.2
Attaching screenshot of the error. Any help/solution would be highly appreciated.
linux ubuntu 64-bit node.js
edited Jan 9 at 15:02
Tomasz Jakub Rup
618413
asked Jan 9 at 14:00
Saloni YadavSaloni Yadav
12
add a comment |
I am getting the error:
Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (57)
while running gulp command.
I have tried deleting node_modules folder and re-running npm install after running npm cache clean. I have tried the highly recommended npm rebuild node-sass. But, to no avail.
Version information:
- UBUNTU: 18.04.1
- node: 5.4.0
- npm: 3.3.12
- node-sass:
- gulp-sass@2.3.2
- node-sass@3.13.1
- gulp-sass@2.3.2
Attaching screenshot of the error. Any help/solution would be highly appreciated.
linux ubuntu 64-bit node.js
edited Jan 9 at 15:02
Tomasz Jakub Rup
618413
asked Jan 9 at 14:00
Saloni YadavSaloni Yadav
12
Everything is very much out of date.
– Daniel B
Jan 9 at 14:42
Yes but it is my limitation because this is the code my company is using. I can't change/update versions
– Saloni Yadav
Jan 9 at 14:45
You’re out of luck then. Perhaps trynvmto find a version of Node that’s compatible.
– Daniel B
Jan 9 at 14:51
Have you checked the following: github.com/sass/node-sass/issues/2142 (The official GitHub repository of this specific package with an issue much like yours). Also, from memory I recall having the remove the contents of my node_modules folder and running npm install again (though you might want to backup the node_modules folder)
– Paul
Jan 9 at 15:52
None of it worked.. later I ran npm install gulp --g instead of sudo apt install gulp and my project started working :D
– Saloni Yadav
Jan 9 at 16:17
add a comment |
I am getting the error:
Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (57)
while running gulp command.
I have tried deleting node_modules folder and re-running npm install after running npm cache clean. I have tried the highly recommended npm rebuild node-sass. But, to no avail.
Version information:
- UBUNTU: 18.04.1
- node: 5.4.0
- npm: 3.3.12
- node-sass:
- gulp-sass@2.3.2
- node-sass@3.13.1
- gulp-sass@2.3.2
Attaching screenshot of the error. Any help/solution would be highly appreciated.
linux ubuntu 64-bit node.js
edited Jan 9 at 15:02
Tomasz Jakub Rup
618413
asked Jan 9 at 14:00
Saloni YadavSaloni Yadav
12
I am getting the error:
Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (57)
while running gulp command.
I have tried deleting node_modules folder and re-running npm install after running npm cache clean. I have tried the highly recommended npm rebuild node-sass. But, to no avail.
Version information:
- UBUNTU: 18.04.1
- node: 5.4.0
- npm: 3.3.12
- node-sass:
- gulp-sass@2.3.2
- node-sass@3.13.1
- gulp-sass@2.3.2
Attaching screenshot of the error. Any help/solution would be highly appreciated.
linux ubuntu 64-bit node.js
linux ubuntu 64-bit node.js
edited Jan 9 at 15:02
Tomasz Jakub Rup
618413
asked Jan 9 at 14:00
Saloni YadavSaloni Yadav
12
edited Jan 9 at 15:02
Tomasz Jakub Rup
618413
asked Jan 9 at 14:00
Saloni YadavSaloni Yadav
12
edited Jan 9 at 15:02
Tomasz Jakub Rup
618413
edited Jan 9 at 15:02
Tomasz Jakub Rup
618413
edited Jan 9 at 15:02
Tomasz Jakub Rup
618413
618413
asked Jan 9 at 14:00
Saloni YadavSaloni Yadav
12
asked Jan 9 at 14:00
Saloni YadavSaloni Yadav
12
asked Jan 9 at 14:00
Saloni YadavSaloni Yadav
12
12
Everything is very much out of date.
– Daniel B
Jan 9 at 14:42
Yes but it is my limitation because this is the code my company is using. I can't change/update versions
– Saloni Yadav
Jan 9 at 14:45
You’re out of luck then. Perhaps trynvmto find a version of Node that’s compatible.
– Daniel B
Jan 9 at 14:51
Have you checked the following: github.com/sass/node-sass/issues/2142 (The official GitHub repository of this specific package with an issue much like yours). Also, from memory I recall having the remove the contents of my node_modules folder and running npm install again (though you might want to backup the node_modules folder)
– Paul
Jan 9 at 15:52
None of it worked.. later I ran npm install gulp --g instead of sudo apt install gulp and my project started working :D
– Saloni Yadav
Jan 9 at 16:17
add a comment |
Everything is very much out of date.
– Daniel B
Jan 9 at 14:42
Yes but it is my limitation because this is the code my company is using. I can't change/update versions
– Saloni Yadav
Jan 9 at 14:45
You’re out of luck then. Perhaps trynvmto find a version of Node that’s compatible.
– Daniel B
Jan 9 at 14:51
Have you checked the following: github.com/sass/node-sass/issues/2142 (The official GitHub repository of this specific package with an issue much like yours). Also, from memory I recall having the remove the contents of my node_modules folder and running npm install again (though you might want to backup the node_modules folder)
– Paul
Jan 9 at 15:52
None of it worked.. later I ran npm install gulp --g instead of sudo apt install gulp and my project started working :D
– Saloni Yadav
Jan 9 at 16:17
Everything is very much out of date.
– Daniel B
Jan 9 at 14:42
Everything is very much out of date.
– Daniel B
Jan 9 at 14:42
Yes but it is my limitation because this is the code my company is using. I can't change/update versions
– Saloni Yadav
Jan 9 at 14:45
Yes but it is my limitation because this is the code my company is using. I can't change/update versions
– Saloni Yadav
Jan 9 at 14:45
You’re out of luck then. Perhaps try
nvm to find a version of Node that’s compatible.– Daniel B
Jan 9 at 14:51
You’re out of luck then. Perhaps try
nvm to find a version of Node that’s compatible.– Daniel B
Jan 9 at 14:51
Have you checked the following: github.com/sass/node-sass/issues/2142 (The official GitHub repository of this specific package with an issue much like yours). Also, from memory I recall having the remove the contents of my node_modules folder and running npm install again (though you might want to backup the node_modules folder)
– Paul
Jan 9 at 15:52
Have you checked the following: github.com/sass/node-sass/issues/2142 (The official GitHub repository of this specific package with an issue much like yours). Also, from memory I recall having the remove the contents of my node_modules folder and running npm install again (though you might want to backup the node_modules folder)
– Paul
Jan 9 at 15:52
None of it worked.. later I ran npm install gulp --g instead of sudo apt install gulp and my project started working :D
– Saloni Yadav
Jan 9 at 16:17
None of it worked.. later I ran npm install gulp --g instead of sudo apt install gulp and my project started working :D
– Saloni Yadav
Jan 9 at 16:17
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
});
}
});
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%2f1392302%2fnode-sass-does-not-yet-support-your-current-environment-linux-64-bit-with-unsup%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
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%2f1392302%2fnode-sass-does-not-yet-support-your-current-environment-linux-64-bit-with-unsup%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
Everything is very much out of date.
– Daniel B
Jan 9 at 14:42
Yes but it is my limitation because this is the code my company is using. I can't change/update versions
– Saloni Yadav
Jan 9 at 14:45
You’re out of luck then. Perhaps try
nvmto find a version of Node that’s compatible.– Daniel B
Jan 9 at 14:51
Have you checked the following: github.com/sass/node-sass/issues/2142 (The official GitHub repository of this specific package with an issue much like yours). Also, from memory I recall having the remove the contents of my node_modules folder and running npm install again (though you might want to backup the node_modules folder)
– Paul
Jan 9 at 15:52
None of it worked.. later I ran npm install gulp --g instead of sudo apt install gulp and my project started working :D
– Saloni Yadav
Jan 9 at 16:17