microsoft / microsoft/vscode-edge-devtools
The compiler option "strict" should be enabled to reduce type errors
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 827
- Forks
- 358
- Avg merge
- 20h 32m
- Merged PRs (30d)
- 10
Description
Environment (please complete the following information):
- OS (e.g., Windows 10): Kubuntu 22.04 LTS x86_64
- Extension version (e.g., 1.2.3): 2.1.0
Describe the bug:
I am not entirely sure why this happens, but it seems like some extension's internal linter rules get bleeded outside into my project, and i am ending up seeing the error like this on all of my tsconfig files:
The compiler option "strict" should be enabled to reduce type errors

The annotation suggests the error comes from this extension. After disabling the extension the error goes away.
Repro steps:
I don't have any specific steps to reproduce, i have a monorepo project with base tsconfig files, and couple of packages, nothing outstanding really, which makes it even more confusing. However i have a lockfile to share, perhaps some package causing this https://gist.github.com/isRyven/e84f313b36f21126b6a73627efde3b67
Expected behavior:
Additional context:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the diagnostic with the extension enabled in the reported monorepo, using its base tsconfig files and package lockfile, then compare the result after disabling the extension. The issue provides no source file or test entry point, so first locate where the extension reports TypeScript diagnostics. Done means the extension no longer surfaces the strict-option warning in unrelated project tsconfig files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100