-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
refactor: remove warnings by upgrading dependencies #1761
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
base: alpha
Are you sure you want to change the base?
Conversation
Thanks for opening this PR! I think we discussed this already somewhere, but switching to yarn is something we would need to look at, because of potential CI implications and cross-repo compatibility (we don't use it anywhere else to my knowledge). Maybe to break this down into smaller packages, I would stick with npm for the time being and discuss a potential move to yarn in a separate issue. |
I can probably switch back to npm. There was some problem which I think was resolved since then. |
That would be good. |
Thanks for opening this pull request!
|
@romanbsd There are a bunch of conflicts here, would you want to switch from yarn to npm and resolve these? Then I would take care of testing the dashboard. |
New Pull Request Checklist
Issue Description
Update code to the current versions of 3rd party dependencies and standards.
Related issue: #1679
Approach
Following current React practices
TODOs before merging