Stuck on an issue?
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.
[import/no-extraneous-dependencies] Problems when only using types
See original GitHub issueWe’ve started to see failures when moving from 2.18.2 to 2.20.0 regarding importing only types from devDependencies in TypeScript source code. Previously the rule wasn’t triggering for these (which I would expect), but it now is.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:41 (21 by maintainers)
Top Results From Across the Web
Why (and How Can I FIx) ESLint import/no-extraneous ...
As far as I can tell, there is no issue with your package.json, ... 'Definition for rule 'import/no-extraneous-dependencies' was not found'.
Read more >A Guide to ESLint | Laurie on Tech
While this is helpful, some rules need to get more specific. For example, ESLint has a rule called import/no-extraneous-dependencies . The goal ...
Read more >eslint/eslint - Gitter
Having some weird path issues with eslint. Robert Main. @rmainseas ... Run 'npm i -S assert' to add it import/no-extraneous-dependencies. Roy Sutton.
Read more >eslint-plugin-import - npm
Start using eslint-plugin-import in your project by running `npm i ... Forbid the use of extraneous packages ( no-extraneous-dependencies ) ...
Read more >Vite and @vitejs/plugin-vue as devDependencies - Reddit
'vite' should be listed in the project's dependencies, not devDependencies. This is the ESlint error type: eslint-plugin-import/no-extraneous- ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Is there a way to suppress this error when using new TS syntax
import type ...? Or any other workaround apart from naming all the modules inimport/internal-regex?causes
ESLint: 'aws-lambda' should be listed in the project's dependencies. Run 'npm i -S aws-lambda' to add it(import/no-extraneous-dependencies)in my devDependencies
Created the PR and added tests.