Node app in Heroku: Module build failed: Error: Unexpected “space” found
I have a node app that has been live on Heroku for a year, but the last update is now crashing on build. I haven't seen this error before and can't find any help.
Here is the error log:
yarn run v1.12.3
$ react-scripts build
Creating an optimized production build...
Failed to compile.
./src/components/Admin_Navigation/navigation.css
Module build failed: Error: Unexpected "space" found.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sonar@1.0.0 heroku-postbuild: `yarn build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sonar@1.0.0 heroku-postbuild script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/npmcache.22xgq/_logs/2018-11-22T00_36_38_522Z-debug.log
-----> Build failed
We're sorry this build is failing! You can troubleshoot common issues here:
https://devcenter.heroku.com/articles/troubleshooting-node-deploys
Some possible problems:
- Dangerous semver range (>) in engines.node
https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
Love,
Heroku
! Push rejected, failed to compile Node.js app.
! Push failed
I've tried the following:
- Update Yarn Lock
- Update package.JSON
- Updated Yarn & Node versions
Any of your thoughts are appreciated. Thanks
Update: this is caused by an unnecessary space in CSS. You can manually look through the CSS for the space, or a less optimal solution is to roll back Node to a version that is less syntax-rigid.
javascript node.js heroku
asked Nov 22 '18 at 0:48
Israel PeckIsrael Peck
557
add a comment |
I have a node app that has been live on Heroku for a year, but the last update is now crashing on build. I haven't seen this error before and can't find any help.
Here is the error log:
yarn run v1.12.3
$ react-scripts build
Creating an optimized production build...
Failed to compile.
./src/components/Admin_Navigation/navigation.css
Module build failed: Error: Unexpected "space" found.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sonar@1.0.0 heroku-postbuild: `yarn build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sonar@1.0.0 heroku-postbuild script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/npmcache.22xgq/_logs/2018-11-22T00_36_38_522Z-debug.log
-----> Build failed
We're sorry this build is failing! You can troubleshoot common issues here:
https://devcenter.heroku.com/articles/troubleshooting-node-deploys
Some possible problems:
- Dangerous semver range (>) in engines.node
https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
Love,
Heroku
! Push rejected, failed to compile Node.js app.
! Push failed
I've tried the following:
- Update Yarn Lock
- Update package.JSON
- Updated Yarn & Node versions
Any of your thoughts are appreciated. Thanks
Update: this is caused by an unnecessary space in CSS. You can manually look through the CSS for the space, or a less optimal solution is to roll back Node to a version that is less syntax-rigid.
javascript node.js heroku
asked Nov 22 '18 at 0:48
Israel PeckIsrael Peck
557
Any better explanation found? How did you solve it? I am currently using the version of node that I am using locally in my engines dependency of package.json, but I am still getting the same problem
– Aklank Jain
Mar 13 at 5:49
add a comment |
I have a node app that has been live on Heroku for a year, but the last update is now crashing on build. I haven't seen this error before and can't find any help.
Here is the error log:
yarn run v1.12.3
$ react-scripts build
Creating an optimized production build...
Failed to compile.
./src/components/Admin_Navigation/navigation.css
Module build failed: Error: Unexpected "space" found.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sonar@1.0.0 heroku-postbuild: `yarn build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sonar@1.0.0 heroku-postbuild script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/npmcache.22xgq/_logs/2018-11-22T00_36_38_522Z-debug.log
-----> Build failed
We're sorry this build is failing! You can troubleshoot common issues here:
https://devcenter.heroku.com/articles/troubleshooting-node-deploys
Some possible problems:
- Dangerous semver range (>) in engines.node
https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
Love,
Heroku
! Push rejected, failed to compile Node.js app.
! Push failed
I've tried the following:
- Update Yarn Lock
- Update package.JSON
- Updated Yarn & Node versions
Any of your thoughts are appreciated. Thanks
Update: this is caused by an unnecessary space in CSS. You can manually look through the CSS for the space, or a less optimal solution is to roll back Node to a version that is less syntax-rigid.
javascript node.js heroku
asked Nov 22 '18 at 0:48
Israel PeckIsrael Peck
557
I have a node app that has been live on Heroku for a year, but the last update is now crashing on build. I haven't seen this error before and can't find any help.
Here is the error log:
yarn run v1.12.3
$ react-scripts build
Creating an optimized production build...
Failed to compile.
./src/components/Admin_Navigation/navigation.css
Module build failed: Error: Unexpected "space" found.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sonar@1.0.0 heroku-postbuild: `yarn build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sonar@1.0.0 heroku-postbuild script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/npmcache.22xgq/_logs/2018-11-22T00_36_38_522Z-debug.log
-----> Build failed
We're sorry this build is failing! You can troubleshoot common issues here:
https://devcenter.heroku.com/articles/troubleshooting-node-deploys
Some possible problems:
- Dangerous semver range (>) in engines.node
https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
Love,
Heroku
! Push rejected, failed to compile Node.js app.
! Push failed
I've tried the following:
- Update Yarn Lock
- Update package.JSON
- Updated Yarn & Node versions
Any of your thoughts are appreciated. Thanks
Update: this is caused by an unnecessary space in CSS. You can manually look through the CSS for the space, or a less optimal solution is to roll back Node to a version that is less syntax-rigid.
javascript node.js heroku
javascript node.js heroku
asked Nov 22 '18 at 0:48
Israel PeckIsrael Peck
557
asked Nov 22 '18 at 0:48
Israel PeckIsrael Peck
557
edited Mar 22 at 15:55
Israel Peck
asked Nov 22 '18 at 0:48
Israel PeckIsrael Peck
557
asked Nov 22 '18 at 0:48
Israel PeckIsrael Peck
557
asked Nov 22 '18 at 0:48
Israel PeckIsrael Peck
557
557
Any better explanation found? How did you solve it? I am currently using the version of node that I am using locally in my engines dependency of package.json, but I am still getting the same problem
– Aklank Jain
Mar 13 at 5:49
add a comment |
Any better explanation found? How did you solve it? I am currently using the version of node that I am using locally in my engines dependency of package.json, but I am still getting the same problem
– Aklank Jain
Mar 13 at 5:49
Any better explanation found? How did you solve it? I am currently using the version of node that I am using locally in my engines dependency of package.json, but I am still getting the same problem
– Aklank Jain
Mar 13 at 5:49
Any better explanation found? How did you solve it? I am currently using the version of node that I am using locally in my engines dependency of package.json, but I am still getting the same problem
– Aklank Jain
Mar 13 at 5:49
add a comment |
1 Answer
1
active
oldest
votes
I faced a similar problem to this, what helped me was to go line by line in searching for the problem, and in the end it was an unintended space between : and hover in the CSS file that was causing the problem.
It was surprising since that code I never changed and it was working before but the solution was to actually find the space being talked about in my CSS file.
edited Mar 22 at 16:04
montrealist
3,03483953
answered Mar 13 at 8:23
Aklank JainAklank Jain
361211
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%2f53422447%2fnode-app-in-heroku-module-build-failed-error-unexpected-space-found%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
I faced a similar problem to this, what helped me was to go line by line in searching for the problem, and in the end it was an unintended space between : and hover in the CSS file that was causing the problem.
It was surprising since that code I never changed and it was working before but the solution was to actually find the space being talked about in my CSS file.
edited Mar 22 at 16:04
montrealist
3,03483953
answered Mar 13 at 8:23
Aklank JainAklank Jain
361211
add a comment |
I faced a similar problem to this, what helped me was to go line by line in searching for the problem, and in the end it was an unintended space between : and hover in the CSS file that was causing the problem.
It was surprising since that code I never changed and it was working before but the solution was to actually find the space being talked about in my CSS file.
edited Mar 22 at 16:04
montrealist
3,03483953
answered Mar 13 at 8:23
Aklank JainAklank Jain
361211
add a comment |
I faced a similar problem to this, what helped me was to go line by line in searching for the problem, and in the end it was an unintended space between : and hover in the CSS file that was causing the problem.
It was surprising since that code I never changed and it was working before but the solution was to actually find the space being talked about in my CSS file.
edited Mar 22 at 16:04
montrealist
3,03483953
answered Mar 13 at 8:23
Aklank JainAklank Jain
361211
I faced a similar problem to this, what helped me was to go line by line in searching for the problem, and in the end it was an unintended space between : and hover in the CSS file that was causing the problem.
It was surprising since that code I never changed and it was working before but the solution was to actually find the space being talked about in my CSS file.
edited Mar 22 at 16:04
montrealist
3,03483953
answered Mar 13 at 8:23
Aklank JainAklank Jain
361211
edited Mar 22 at 16:04
montrealist
3,03483953
edited Mar 22 at 16:04
montrealist
3,03483953
edited Mar 22 at 16:04
montrealist
3,03483953
3,03483953
answered Mar 13 at 8:23
Aklank JainAklank Jain
361211
answered Mar 13 at 8:23
Aklank JainAklank Jain
361211
answered Mar 13 at 8:23
Aklank JainAklank Jain
361211
361211
add a comment |
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%2f53422447%2fnode-app-in-heroku-module-build-failed-error-unexpected-space-found%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
Any better explanation found? How did you solve it? I am currently using the version of node that I am using locally in my engines dependency of package.json, but I am still getting the same problem
– Aklank Jain
Mar 13 at 5:49