[peer dependencies] Fix some warnings related to peer dependencies #295
Conversation
Yarn provides some useful warnings once the dependencies are resolved. In some cases, it was possible to update versions of dependencies to satisfy the warnings, in some other cases I found the dependencies in question were no longer apparently used anywhere, and so I removed them. In some cases I moved "dev" dependencies to the root package.json since they are applicable to all components in the yarn workspace (e.g. eslint related dependencies). Also some small cleanups like removing "resolution" blocks that had no effect, as well as "engines" and "categories" blocks that are only applicable to the package.json for a vscode extension. Signed-off-by: Marc Dumais <marc.dumais@ericsson.com>
|
IP Tickets for the dependencies that fail the license check: This content is either not correctly mapped by the system, or requires review. |
Signed-off-by: Marc Dumais <marc.dumais@ericsson.com>
marcdumais-work
force-pushed
the
fix-peer-deps
branch
from
88c4f89 to
8db9b8e
Compare
What it does
Yarn provides some useful warnings once the dependencies are resolved. In some cases, it was possible to update versions of dependencies to satisfy the warnings, in some other cases I found the dependencies in question were no longer apparently used anywhere, and so I removed them.
In some cases I moved "dev" dependencies to the root package.json since they are applicable to all components in the yarn workspace (e.g. eslint related dependencies).
Also some small cleanups like removing "resolution" blocks that had no effect, as well as "engines" and "categories" blocks that are only applicable to the package.json for a vscode extension.
How to test
Make sure the repo still builds and that the tests pass.
Follow-ups
N/A
Review checklist