Last 12 weeks · 0 commits
2 of 6 standards met
Summary add an explicit allowlist for the three public TSConfig files exclude repository-only files such as and from the published package Why Without a field, npm includes all eligible repository files by default. The package only exposes the three root TSConfig files, so an allowlist keeps the published artifact intentional without changing any documented consumer paths. Validation confirmed the tarball contains , , and , plus npm's automatically included , , and
{ "extends": "@vue/tsconfig/tsconfig.dom.json", "include": ["env.d.ts", "src/*/", "src/*/.vue"], "exclude": ["src/*/__tests__/"], "compilerOptions": { // Extra safety for array and object lookups, but may have false positives. "noUncheckedIndexedAccess": true, // Path mapping for cleaner imports. "paths": { "@/": ["./src/"] } } }
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: 360, Forks: 29. License: MIT. Latest release: v0.9.1 (5mo ago). Open PRs: 1, open issues: 1. Last activity: 5mo ago. Community health: 37%. Top contributors: haoqunjiang, joerick, lupas, moznion, ntnyq, sgpinkus, yionr, Slessi.