Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/analyze.ts`:
- Around line 406-412: The string-parsing logic using inString and extraNamesStr
misclassifies quotes preceded by an even number of backslashes because it only
checks extraNamesStr[i - 1] !== "\\"; update the condition where you toggle
inString (the block that checks if char === inString) to count consecutive
backslashes immediately before index i (walking backwards from i-1) and only
treat the quote as escaped when the count is odd; use the existing variables
(inString, char, i, extraNamesStr) so the quote closes the string when the
preceding-backslash count is even (including zero).

---

Nitpick comments:
In `@test/exports.test.ts`:
- Around line 109-124: Add a new mixed-separator test case to the exports tests
that ensures a function-call comma and a declarator comma coexist: add the
string "export const a = fn('x', async () => {}), b = 1" as a case similar to
the existing entries and assert its parsed result is { type: "declaration",
name: "a", names: ["a", "b"] } so the helper correctly returns both declarator
names; update the test array alongside the entries for
useSleep/handler/middleware.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/analyze.ts`:
- Around line 424-437: The comma-separation logic in _extractExtraNames
incorrectly treats commas inside TypeScript generics as top-level separators;
update the loop that tracks bracket nesting (currently using depth and
extraNamesStr) to also track angle bracket nesting by adding an angleDepth
counter that increments on '<' and decrements on '>', and change the comma check
to only treat a comma as a real separator when depth === 0 and angleDepth === 0;
make sure to reference the same loop and variables (_extractExtraNames,
extraNamesStr, depth) so the new angleDepth is updated alongside existing
bracket handling.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/analyze.ts`:
- Around line 431-433: The code currently sets inTypeAnnotation = false on any
top-level '=' (char === "=") which incorrectly closes type annotations for arrow
types like '=>'; update the condition so '=' only ends the type annotation when
it is not part of an arrow token. Concretely, when evaluating char === "=", also
check neighboring characters (e.g., the previous and next characters via
source[index-1] and source[index+1] or whatever context variables exist) and
skip setting inTypeAnnotation = false if the '=' is part of '=>'. Keep the
original depth and angleDepth checks and only suppress the state change for
arrow '=>' sequences.