The AWS public build job is failing due to not being able to find "msw". I believe this is because when building it in docker we don't get any of the packages that are only in partners. When building it locally it installs all of the dev dependencies when doing yarn install at the root level. In Docker we only know the packages in the sites/public directory
How Can This Be Tested/Reviewed?
I have not been able to successfully test this locally because I get this error The chromium binary is not available for arm64.. I'm still working through how to get over that step. But since this is blocking the AWS pipeline I think it's worth it to gamble on this fix
Author Checklist:
[ ] Added QA notes to the issue with applicable URLs
[ ] Reviewed in a desktop view
[ ] Reviewed in a mobile view
[ ] Reviewed considering accessibility
[ ] Added tests covering the changes
[ ] Made corresponding changes to the documentation
[ ] Ran yarn generate:client and/or created a migration when required
Review Process:
Read and understand the issue
Ensure the author has added QA notes
Review the code itself from a style point of view
Pull the changes down locally and test that the acceptance criteria is met
Either (1) explicitly ask a clarifying question, (2) request changes, or (3) approve the PR, even if there are very small remaining changes, if you don't need to re-review after the updates
Description
The AWS public build job is failing due to not being able to find "msw". I believe this is because when building it in docker we don't get any of the packages that are only in partners. When building it locally it installs all of the dev dependencies when doing
yarn installat the root level. In Docker we only know the packages in the sites/public directoryHow Can This Be Tested/Reviewed?
I have not been able to successfully test this locally because I get this error
The chromium binary is not available for arm64.. I'm still working through how to get over that step. But since this is blocking the AWS pipeline I think it's worth it to gamble on this fixAuthor Checklist:
yarn generate:clientand/or created a migration when requiredReview Process: