From d49ee777d61b5d592836b48d1d55d054c0133469 Mon Sep 17 00:00:00 2001 From: Jacob Bare Date: Thu, 23 Feb 2023 13:40:40 -0600 Subject: [PATCH] Update MIGRATING.md --- MIGRATING.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/MIGRATING.md b/MIGRATING.md index f68d089e8..3063278c2 100644 --- a/MIGRATING.md +++ b/MIGRATING.md @@ -150,7 +150,13 @@ If the website's dev server is running, this will _not_ automatically restart th Note: all of the below files are located in the `.github/workflows` folder. ### Action Items -1. Update the `node-ci.yml` file to the following: +0. Create the `tests/integration.js` file in the root of the repository with the following contents + ```js + // eslint-disable-next-line + require('@parameter1/base-cms-marko-web/integration/test-website-boot'); + + ``` +2. Update the `node-ci.yml` file to the following: ```yml name: Node.js CI @@ -436,7 +442,7 @@ The internal `eslint` version was upgrade from v5 to v8 -- quite a large jump -- - In the root `package.json` add or update the following devDependencies: (**note:** newsletter and export repos do _not_ need `@babel/core`, `@babel/eslint-parser` or `eslint-plugin-vue`) ```json "@parameter1/base-cms-eslint": "^4.1.0", - "@parameter1/browserslist-config-base-cms": "^4.1.0", + "@parameter1/browserslist-config-base-cms": "^4.1.0", ``` - You must **remove** _all_ `babel-eslint` packages, since `@babel/eslint-parser` is now used under the hood - Double-check your website and global package files and ensure there aren't any references to eslint or any of it's plugins - this way only the root version will be used.