-
Notifications
You must be signed in to change notification settings - Fork 157
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
Convert to yarn for package management #3952
Conversation
a7b83d1
to
7480d36
Compare
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.
Did upgrading eslint cause all those typescript errors? If we can get rid of the new @ts-ignore
s we should
Yeah it looks like the yarn.lock is using the react v18 types which seem to introduce these issues bvaughn/react-error-boundary#111 (comment) If we can bump it back to 17.x in the yarn.lock somehow it will mirror the package-lock and we can maybe revert the code changes. |
Using https://classic.yarnpkg.com/en/docs/cli/import/ preserves the @types/react at 17 at least, might have other issues, did a quick test with
|
I tried removing most of these, but the |
Here is a summary of the
|
Yeah.. it looks like we've bumped up to 18 for
|
I had no idea about |
There were still some v18 deps in the new yarn.lock which was odd, it seems to use the state of node_modules too, so did a clean run and that brought the rest back down to v17. Can remove the ts-ignore and the other code changes too, but the rest all seem like improvements 👍 . |
- git checkout main - rm -rf node_modules - make node_modules - yarn import
Closes #3943
Moves Core to use the same package manager as EE. This is really only to enforce consistency; we chose
yarn
as it a bit faster (historically) and has a nicer UX.Note: Some scripts that run during releases may still be
npm
to reduce the risk of finding issues during a release.