-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Support for bundledDependencies #1436
Labels
Comments
Absolutely things in bundledDependencies should not error; that seems like an (albeit very very rare) omission. A PR adding that support is welcome. |
Thanks for the quick answer. Just started to work on the PR. Comments are welcome. I will try to do more tomorrow. |
schmidsi
added a commit
to schmidsi/eslint-plugin-import
that referenced
this issue
Aug 4, 2019
schmidsi
added a commit
to schmidsi/eslint-plugin-import
that referenced
this issue
Aug 4, 2019
- Make tests pass. - Fixes import-js#1436.
schmidsi
added a commit
to schmidsi/eslint-plugin-import
that referenced
this issue
Aug 8, 2019
schmidsi
added a commit
to schmidsi/eslint-plugin-import
that referenced
this issue
Aug 8, 2019
- Make tests pass. - Fixes import-js#1436.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have some auto-generated code (through https://github.com/prisma/photonjs) that is located in
node_modules/@generated/photon
.How can I tell
eslint-plugin-import
to not throw aimport/no-extraneous-dependencies
error? The best solution I can think of so far is to put it into the bundledDependencies. But it seems likeeslint-plugin-import
does not look at these.Related: prisma/prisma#314
The text was updated successfully, but these errors were encountered: