Adding a yarn.lock file for the website that works (i.e. the website builds successfully).
Why
While we do block unnecessary yarn.lock files in random folders, it seems the website one might be necessary.
It looks like there may have been a breaking change in a cheerio package that we're picking up when the CI builds because, without a yarn lock to keep us on known good dependency versions, we get a broken cheerio package.
Description
Adding a
yarn.lockfile for thewebsitethat works (i.e. the website builds successfully).Why
While we do block unnecessary
yarn.lockfiles in random folders, it seems thewebsiteone might be necessary.It looks like there may have been a breaking change in a
cheeriopackage that we're picking up when the CI builds because, without a yarn lock to keep us on known good dependency versions, we get a broken cheerio package.Resolves #956
Screenshots
N/A
Microsoft Reviewers: Open in CodeFlow