Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Typescript!
See original GitHub issueIs your feature request related to a problem? Please describe.
I’m always frustrated when try to be the first one to use typescript with eslint-plugin-boundaries 😀
Describe the solution you’d like
debugging eslint-plugin-boundaries I found it’s using const resolve = require("eslint-module-utils/resolve").default; to resolve import paths which lead me to typescript section https://github.com/benmosher/eslint-plugin-import#typescript
so long story short adding - plugin:import/typescript # this line does the trick to extends works!
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@javierbrea thanks a lot for your quick response! 🌟 I’m not sure I can help with the contribution, but I’ll share my example TS project that I’m unable to get working.
I try to use this plugin with my typescript project, and it’s definitely not working with TS paths aliases. When I added https://www.npmjs.com/package/eslint-import-resolver-typescript, it starts throwing strange errors:
Can you document how to use this plugin with typescript?
Related: https://stackoverflow.com/questions/57032522/eslint-complains-about-typescripts-path-aliasing