ES6 Template Strings and no-unused-vars aren't (competely) compatible
See original GitHub issuevar who = "Paul";
module.exports = `Hello ${who}!`;
Linting that results in a warning that who is defined but never used
. My human eyes can tell you that’s wrong but I’m not actually sure if esprima provides enough info to also tell us that.
This is using v0.11.0-alpha.0 and config using ES6.
Issue Analytics
- State:
- Created 9 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
no-unused-vars - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >Why do I get an unexpected template string expression error?
This is an warning generated by ESLint: no-template-curly-in-string. Disallow template literal placeholder syntax in regular strings ...
Read more >8. Template literals - Exploring JS
ES6 has two new kinds of literals: template literals and tagged template literals. ... non-standard and breaks compatibility with the rest of the...
Read more >Template literals (Template strings) - JavaScript | MDN
Template literals are literals delimited with backtick (`) characters, allowing for multi-line strings, string interpolation with embedded ...
Read more >Getting Literal With ES6 Template Strings - Chrome Developers
Substitution allows us to take any valid JavaScript expression (including say, the addition of variables) and inside a Template Literal, the ...
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
@seemsindie @KeitIG Please stop by our Gitter chat if you need help with this. Thanks!
Working on this.