-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
eslint: bring back no-implicit-dependencies rule #7079
Comments
Worst case scenario we could try to implement our own rule within the repo. |
If we remove whitelisting how much duplication it causes, can we somehow catch duplicate versions? |
We could use peer dependencies, it should mitigate duplication. |
But it will break the end product if a version does not match with core? I meant to check that we have exactly the same versions across the repo. Actually @kittaakos built something like that Line 48 in d54c2f0
|
Fixing this issue will also fix bundling issues for electron we are having on theia-apps. @akosyakov I will do like you mentioned and make all implicit dependencies explicit, with a script to make sure the same range is used across the repo. |
Description
When I migrated the rules from tslint to eslint, I did not find a
no-implicit-dependency
rule that could be configured the same way we used to have it on tslint.Current rules I found to prevent implicit dependencies:
Old rule used to whitelist the following packages:
The text was updated successfully, but these errors were encountered: