The build of the admin app should be successfull
I tried to update my existing project with yarn upgrade and then run yarn webiny deploy apps --env=prod again and the build failed (no problems with api though)
Then I created a new project to check if this is a problem with my cd pipeline and got the same error there:
This is the first deploy of prod environment, so it may take a few minutes.
💡 Loaded prod environment from <projectRoot>/.env.json.
✔ Great! Your MongoDB is accessible.
webiny Collecting components from the template. +0ms
webiny Executing the template's components graph. +33ms
webiny:lambdaRole Creating role 'b01ee561_upgradetest_apps_prod_lambdaRole'. +0ms
webiny:lambdaRole Role 'b01ee561_upgradetest_apps_prod_lambdaRole' was successfully deployed to region 'eu-central-1'. +21sng...
webiny:admin Building 'admin' +0ms
error Command failed with exit code 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npx create-webiny-project upgradetest --template=cmsyarn webiny deploy api --env=prodyarn webiny deploy apps --env=prodWill take a look now @jcode-hub.
@doitadrian Checked on my admin, and it relates to https://github.com/webiny/webiny-js/issues/1247
I see, I can see this in my yarn start, in a brand new project:

(which is what is shown in #1247 - thanks @latotty )
At first, this looks to me like some 3rd party dependency got changed. Because this is a brand new issue, and I'm pretty sure nothing has changed in this department on our side.
Let me take a look deeper into what we can do about it.
@doitadrian thanks! I'm getting the error too. At first I thaught it was related to my own changes but when I pulled the master branch to update it, the error came up then.
The 4.12.1 is up, please give it a try (I tried it already on my own machine).
Thanks @TommyJackson85 @latotty @jcode-hub!
@doitadrian thanks, working for me also 👍
BTW: the pipeline's "Deploy Apps stack" step fails https://github.com/webiny/webiny-js/runs/1127692810?check_suite_focus=true
I can also confirm the fix worked! Nice, many thanks @doitadrian and the team!
Nice guys! 🎉
BTW @latotty, yeah, saw that one, which immediately got me concerned that something went wrong again, and that's why I immediately tried the new version locally.
Not sure why it failed, especially because while releasing 4.12.1.beta.0, everything was OK.
Will have to debug this one.
Great work! Thanks! It's up and running for me again!
Most helpful comment
The 4.12.1 is up, please give it a try (I tried it already on my own machine).
Thanks @TommyJackson85 @latotty @jcode-hub!