Open paul-marechal opened 4 years ago
cc @vince-fugnitto
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.
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 https://github.com/eclipse-theia/theia/blob/d54c2f0d7307ef504e9c46e490f4ebd0ac06ef51/package.json#L48. So maybe we just check it more regularly or fail a build if there are different versions in some packages.
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: