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.
1.2.0 - Cannot read tslint configuration - 'linterConfiguration.rules.delete is not a function'
See original GitHub issue- tslint Version: 5.17.0
- typescript Version: 3.5.1
Steps to Reproduce:
- Create new Microsoft SPFx 2016 onPrem solution (
yo @microsoft/sharepoint) - Remove invalid extends configuration from
tslint.json(Line 2) - Open
.ts-file - Check VSCode Problems Output:
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (3 by maintainers)
Top Results From Across the Web
1.2.0 - Cannot read tslint configuration - GitHub
1.2.0 - Cannot read tslint configuration - 'linterConfiguration.rules.delete is not a function' #109.
Read more >tslint is not working in visual studio code - Stack Overflow
It means that you are missing tslint config file. tslint.json Here is a guide on how to config it it ...
Read more >Configuring TSLint - Palantir Open Source
When using the CLI or many third-party tools, a file named tslint.json or tslint.yaml is used to configure which rules get run and...
Read more >types/react-native-ad-manager 1.2.1 on npm - Libraries.io
The linter configuration file, tslint.json should contain { "extends": "dtslint/dt.json" } , and no additional rules.
Read more >tslint - npm
custom formatters (failure reporters); inline disabling and enabling of rules with comment flags in source code; configuration presets ( tslint: ...
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
Fix for me was clicking the typescript version box on the bottom right of the toolbar and changing it from “Use VS Code’s Version (3.5.2)” to “Use Workspace Version (2.9.2)”
@mjbvz sorry for the late reply!
I was using this extension.
The problem was that the generated solution uses an outdated version of tslint, once I forced that to a current version with yarn everything worked as intended.
The extension didn’t use the global tslint installation.
So, to everyone reading this, make sure that your projects tslint version is up-to-date. And sorry for keeping the solution to myself, I didn’t realize that more people had the problem, I thought I was being stupid.
Shouldn’t the extension use the global (or ideally the most up-to-date) version of tslint that is installed?