-
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
[quality] Implement a custom tslint rule to check imports #467
Comments
An alternative is to move lerna root to another folder, but we've rejected it because of the not standard project setup: #423 (comment) |
I'm wondering how that can be done ? but that would be good indeed. |
There is such check for ESlint: https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-extraneous-dependencies.md I wonder whether we can leverage eslint. It supports ES6 modules. |
OK thx for the pointers... |
Currently, it is really painful for me, because vs code is creating all sorts of wrong imports and I don't see them through watch. So I always run |
I wish someone start working on it, it is exhausting to catch them manually. |
using option
will report issues around test dependencies and import from the current module in tests
|
|
Because of hoisting, any package can access any dependency declared in another package. We should check that imports only access packages declared in package.json or transitive dependencies.
The text was updated successfully, but these errors were encountered: