False 'unused dependency' for asyncawait.
See original GitHub issueWhen importing asyncawait as such:
const async = require('asyncawait').async; const await = require('asyncawait').await;
It says that asyncawait is an unused dependency.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
depcheck | Yarn - Package Manager
Depcheck is a tool for analyzing the dependencies in a project to see: how each dependency is used, which dependencies are useless, and...
Read more >Lindhart.Analyser.MissingAwaitWarning 2.0.0 - NuGet
unused -task-warning. When using dependency injection and async-await pattern it is possible to end up with an interface with a method that ...
Read more >What are unused/undeclared dependencies in Maven? What ...
I was experiencing a false "unused declared dependency" warning for a library, even though I was importing and using a type from it,...
Read more >Async code smells and how to track them down with analyzers
This blog post continues the series which is a guide through the code analyzers available on the market and their possibilities.
Read more >Missing await warning - Visual Studio Marketplace
When using dependency injection and async-await pattern it is ... ProblemSolved; // Will return false - we expected it to return true }...
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 FreeTop 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
Top GitHub Comments
I agree, I think this issue can be closed and that the proper solution is to switch the parser.
I think that
class
have been a reserved keyword since the beginning of JavaScript, which is why Node (or other runtimes) won’t accept that as a variable name.async
andawait
on the other hand was added later to the spec, after the initial release, and thus had to be backwards compatible.