agree with you. The author should give a bit more of context.
What he meant is that in your package.json, under "script" > "build". Whatever command build you have, you should add "CI = false" to override the default value which is "CI=TRUE".
For his example:
"build": "npm run build"
New line will be "build": "CI=false npm run build".
My case I have to write like this "build" : "CI=false && craco build". I used Typescript. Not sure if the && symbol needed or not. I dont bother to test actually :)
But if you only change in package.json and deploy vercel, Preview will be successful (Active) but Production still fails.
So, final solution to solve for both Preview and Production is to add environment variable in Project Settings > Environment Variables in Vercel.
Oh yah, I am self-taught artist and a grandaunt in the internet of things who is building Apps that connect visual arts to software devs. So bring it on n let's go animate the world :)
agree with you. The author should give a bit more of context.
What he meant is that in your package.json, under "script" > "build". Whatever command build you have, you should add "CI = false" to override the default value which is "CI=TRUE".
For his example:
"build": "npm run build"
New line will be "build": "CI=false npm run build".
My case I have to write like this "build" : "CI=false && craco build". I used Typescript. Not sure if the && symbol needed or not. I dont bother to test actually :)
But if you only change in package.json and deploy vercel, Preview will be successful (Active) but Production still fails.
So, final solution to solve for both Preview and Production is to add environment variable in Project Settings > Environment Variables in Vercel.
you guys rock CI=false is the best fix
can also add it directly in vercel directly without adding it to a .env file of your project :)
Thank you, for this.