luke
2
Hi, @h3h394, we released a change today which might be related:
You can test if this is the root cause by changing the build command to the version below which will unset this new CI
environment variable:
CI= npm run build
If that doesn’t resolve the issue and/or if there are any questions, please let us know.
8 Likes