hi there,
the warnings are good to make note of, but are not actually the thing that makes the build fail, generally speaking.
The problem exists here:
1:23:49 AM: $ npm run build
1:23:49 AM: > github-battle@1.0.0 build /opt/build/repo
1:23:49 AM: > SET NODE_ENV=‘production’ && webpack
1:23:49 AM: sh: 1: SET: not found
1:23:49 AM: npm ERR! code ELIFECYCLE
1:23:49 AM: npm ERR! syscall spawn
1:23:49 AM: npm ERR! file sh
1:23:49 AM: npm ERR! errno ENOENT
1:23:49 AM: npm ERR! github-battle@1.0.0 build: SET NODE_ENV='production' && webpack
1:23:49 AM: npm ERR! spawn ENOENT
1:23:49 AM: npm ERR!
the command you are trying to run doesn’t seem to be something we like.
Could you post your package.json please?
Also, this Support Guide contains a ton of useful debugging tips that can likely help.