Skip to content

Commit 032dceb

Browse files
committed
chore: drop stale typecheck-coverage exception for plugin-inspect
inspect no longer needs the composite tsconfig that made it opt out of the typecheck gate; it now typechecks cleanly, so remove the exception (its presence fails verify-typecheck-coverage once the package has a typecheck script).
1 parent a920e20 commit 032dceb

1 file changed

Lines changed: 0 additions & 1 deletion

File tree

scripts/verify-typecheck-coverage.ts

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,6 @@ const WORKSPACE_PATTERNS = ['packages/*', 'plugins/*', 'examples/*', 'starter',
3232
* already has one).
3333
*/
3434
const EXCEPTIONS: Record<string, string> = {
35-
'plugins/inspect': 'tsconfig.json is the only one with composite:true, which makes tsc reject valid cross-package imports (TS6307); also has a couple of unrelated spa/composables type bugs. See plans/README.md "Execution notes" for plan 001.',
3635
'examples/hub-next': 'packages/hub/src/node/host-terminals.ts types a child-process env as NodeJS.ProcessEnv, and Next.js\'s ambient types require a literal NODE_ENV on that interface once this app pulls hub into its program. See plans/README.md "Execution notes" for plan 001.',
3736
'examples/hub-next-minimal': 'Same Next.js + hub NODE_ENV ambient conflict as examples/hub-next; the minimal Next host pulls hub into its program too.',
3837
'docs': 'Nuxt app extending the comark-docs layer: tsconfig.json only holds project references into generated `.nuxt/tsconfig.*.json`, which exist only after `nuxt prepare` resolves the layer, so type-checking it would drag a full Nuxt prepare into the Turbo graph.',

0 commit comments

Comments
 (0)