ERROR: failed to solve: process "/bin/bash -ol pipefail -c npm run build" did not complete successfu
Hi, im trying to deploy mi front end application (REACT JS) in railway, my problem is on the image. ty
30 Replies
Project ID:
e27ad83f-3086-426f-a29e-b4d1e2d50dfde27ad83f-3086-426f-a29e-b4d1e2d50dfd
please follow the Most Common Issue part of this guide
https://help.railway.app/project-help/f9v3gkPQRy4UShk5SnoPDH/getting-your-create-react-app-running-on-railway/qHRsgxa5n57xLp1yVgk9fP
Already try to do that guide and this message appears in the console:
update your react-scripts so you dont have to use legacy ssl
This error is on the railway deploy
send your paackage.json
{
"name": "client",
"version": "0.1.0",
"private": true,
"dependencies": {
"@auth0/auth0-react": "^2.1.0",
"@emotion/react": "^11.11.0",
"@emotion/styled": "^11.11.0",
"@mui/icons-material": "^5.11.16",
"@mui/material": "^5.12.3",
"@mui/styled-engine-sc": "^5.12.0",
"@mui/x-data-grid": "^6.5.0",
"@react-google-maps/api": "^2.18.1",
"@redux-devtools/extension": "^3.2.5",
"@testing-library/jest-dom": "^5.11.10",
"@testing-library/react": "^11.2.6",
"@testing-library/user-event": "^13.1.1",
"axios": "^1.4.0",
"chart.js": "^2.9.4",
"date-fns": "^2.30.0",
"formik": "^2.2.9",
"react": "^17.0.2",
"react-chartjs-2": "^2.11.1",
"react-data-table-component": "^7.5.3",
"react-dom": "^17.0.2",
"react-loader-spinner": "^5.3.4",
"react-redux": "^7.2.3",
"react-responsive-carousel": "^3.2.23",
"react-router-dom": "^6.11.1",
"react-scripts": "^5.0.1",
"redux": "^4.0.5",
"redux-thunk": "^2.3.0",
"serve": "^14.2.0",
"styled-components": "^5.3.10",
"web-vitals": "^2.1.4",
"yup": "^1.2.0"
},
"scripts": {
"dev": "react-scripts start",
"start": "serve build -n -L -p $PORT",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
"eslintConfig": {
"extends": [
"react-app",
"react-app/jest"
]
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
}
}
perfect
okay now you can follow the very last section of that guide
you mean this part?
yep failed to compile
full build logs please
#7 [stage-0 3/10] COPY .nixpacks/nixpkgs-293a28df6d7ff3dec1e61e37cc4ee6e6c0fb0847.nix .nixpacks/nixpkgs-293a28df6d7ff3dec1e61e37cc4ee6e6c0fb0847.nix
#7 CACHED
#8 [stage-0 4/10] RUN nix-env -if .nixpacks/nixpkgs-293a28df6d7ff3dec1e61e37cc4ee6e6c0fb0847.nix && nix-collect-garbage -d
#8 CACHED
#9 [stage-0 5/10] RUN printf '\nPATH=/app/node_modules/.bin:$PATH' >> /root/.profile
#9 DONE 0.5s
#10 [stage-0 6/10] COPY . /app/.
#10 DONE 0.1s
#11 [stage-0 7/10] RUN --mount=type=cache,id=s/e73c272d-4d43-4dfb-a17f-d6f25a3340c7-/root/npm,target=/root/.npm npm i
#11 0.987 npm
WARN config production Use
--omit=dev instead.
#11 34.91 npm WARN deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
#11 36.65 npm WARN deprecated [email protected]: Use your platform's native performance.now() and performance.timeOrigin.
#11 36.86 npm WARN deprecated [email protected]: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
#11 36.97 npm WARN deprecated [email protected]: Please use @jridgewell/sourcemap-codec instead
#11 40.10 npm WARN deprecated [email protected]: [email protected]
#11 45.24 npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x.
#11 82.23
#11 82.23 added 1582 packages, and audited 1583 packages in 1m
#11 82.23
#11 82.23 264 packages are looking for funding
#11 82.23 run npm fund for detailsnot like that, as a .txt file
oh sorry
wait a minute
is not complete
sorry
sending again
full build logs please
^
I had already added to the environment variable
did you redeploy
and did you deploy to the correct service
already redeploy again
and this is the log:
im trying with this: "build": "CI=false react-scripts build", on my package.json
It works!
ty for your help
very odd that setting CI = false in the service variables didn't work, either way, you should work to fix the warnings, they are warnings for a reason and can have unintended effects on your app