Closed joelcarr closed 1 year ago
Maggie asked offline if these changes had been tested in systems like next-article
. I have just tested these changes in next-article
by installing the local version with these changes and running npm run build
, then npm start
, and loading a selection of articles (live blogs, scrollytelling, toppers etc). I have also tested this with next-search-page
with the same instructions and testing the search pages. Everything has been working as expected.
As the changes are purely affecting the build setup and not the published code, which is concern of the other codeowners - I am merging this pull request without review from the other codeowners.
I used x-dash to test the migration script and slowly completed the migration. Performing this migration showed our tests failed on Node 18. I updated Jest and its' associated packages. I then came across some ESLint inconsistencies so I updated ESLint and its' associated packages to fix the inconsistencies. Whilst I was there, added the new
@dotcom-reliability-kit/eslint-config
and@financial-times/eslint-config-next
. I then proceeded to fix the ESLint errors.