Last 12 weeks · 3 commits
2 of 6 standards met
Describe the bug When using with (project references mode), overriding in does not take effect. The type checker still behaves as if . Reproduction tsconfig.json tsconfig.app.json package.json scripts Example code that errors Expected behavior in should override the value from , and array index access should not include in the type. Actual behavior The override is ignored. is still typed as . Workaround Downgrade to which does not include . Environment : 0.8.1 : 3.2.1 : 5.8.3 / 5.9.3 (same issue on both) OS: Windows 10 Additional context Clearing build cache () does not help
Repository: vuejs/tsconfig. Description: Base tsconfig for Vue 3 projects. Stars: 357, Forks: 28. License: MIT. Latest release: v0.8.1 (6mo ago). Open PRs: 1, open issues: 3. Last activity: 3d ago. Community health: 37%. Top contributors: haoqunjiang, joerick, lupas, moznion, ntnyq, sgpinkus, yionr.
https://github.com/vuejs/tsconfig/blob/4a223b286dde66b8e70608b09ee2ca3ed41d76d7/tsconfig.dom.json#L4-L11 This file says that ES2020 is used to align with vite: But Vite uses "baseline" in Vite 7, which means it supports ES syntax from around 2.5 years (30 months) ago. Should probably bump this to ES2022 now?
In a TypeScript project with version , this error is prompted, causing the entire project to fail to compile successfully. It seems to be this submission of https://github.com/vuejs/tsconfig/pull/35 that caused it.
Hi team, I've run into a tricky situation with the new default, specifically around optional boolean props where I need to know if the prop was passed at all. My goal is to differentiate between these two parent usages: 1. `props.showBadgeundefinedprops.showBadgefalseexactOptionalPropertyTypesfalseundefinedexactOptionalPropertyTypesshowBadge: undefined| nullbooleanundefinednull` or other types in the prop definition the recommended way to handle this tri-state boolean pattern now? Or perhaps there's a more elegant approach I'm not seeing. Thanks.