-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade repo to lerna v8 and Node 18 #2209
Conversation
0fe8966
to
93c1808
Compare
5e919ec
to
8d9bb90
Compare
8d9bb90
to
ace7783
Compare
- ie_8 | ||
- ie_9 | ||
- ie_10 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥
@@ -23,6 +23,6 @@ | |||
}, | |||
"devDependencies": { | |||
"@bugsnag/core": "^8.0.0", | |||
"@types/koa": "^2.11.3" | |||
"@types/koa": "2.13.4" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this pinned due to an issue with unit testing? would be good to add a task to update this and validate it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's pinned to the latest version compatible with our current typescript version - this can be reviewed if/when we upgrade typescript
I raised this PR so I can't directly approve it - but I'm happy with the changes so feel free to Approve. 👍🏻 |
Failing PR diff bot test is caused by the removal of the Lerna bootstrap command and should be fine for the next PR |
force-merging with expected PR diff bot failure |
Goal
Upgrades the lerna version from v4 to v8, and upgrades the repo to use Node 18 for devlopment (required by lerna v8)
Design
Upgrading lerna to v8 means removing the deprecated bootstrap command and switching to npm workspaces, which in turn means that packages are now installed into the top-level node_modules directory. Many of the changes within the individual packages are dealing with the fallout of this in order to fix linting, unit tests and typescript errors.
All CI dockerfiles and steps that build the packages also had to be upgraded to node 18 as a result.
Changeset
@types/*
packages to maintain compatibility with the current typescript versionTesting
Covered by a full CI run