fix: stop annotated destructuring from widening the local declaration scan - #570

Problem

The regex scanner that collects locally declared names (RE_EXCLUDE[3]) only ends a declaration at =, ;, \n, of or in. With a TypeScript annotation between the pattern and the =, the destructuring branch can't end at its own bracket. Because of the s flag, the lazy \{.*?\} / \[.*?\] then keeps going across lines until some later }/] happens to come right before =, ; or a newline.

Every identifier in that span is treated as a local declaration, so it is never auto-imported:

const { value }: Props = props

const hooks = [
  useState,
  useEffect,
]

const config = { value }

On main this injects nothing: { value }: Props = props … const config = { value } is captured as one pattern, and useState / useEffect are counted as locals. Array patterns do the same (const [first]: [number] = f() stretches to the next ] followed by = or a newline). A plain annotation like const count: number = 1 also yields count: number rather than count.

This looks like a different trigger for the same widening described in #525. It is not a fix for the for-loop case there, which #522 already handled.

Fix

Match an optional same-line annotation (:[^=;\n]*) outside the captured group, before the terminator. Destructuring patterns now close at their own bracket, and the annotation text is no longer part of the collected names. The annotation can't cross =, ; or a newline, so it can't extend the match.

Tests

• test/existing-scanning.test.ts: annotated simple, object and array declarations, plus two multi-line cases that check the scan stops at the annotated pattern. These 5 cases fail on main.
• test/cases/positive/ts-annotated-destructuring.ts with its snapshot: the end-to-end repro above. It now gets import { useState, useEffect } from 'react'. On main it fails because nothing is injected.

vitest run: 28 files, 260 tests pass. eslint src test and vue-tsc --noEmit are clean.

Summary by CodeRabbit

• Bug Fixes
  • Improved handling of TypeScript type annotations in variable declarations, including destructuring. Variables are now identified correctly, and following array or object declarations are kept separate.