Visitar URL original
Comparing v0.1.64...v0.1.65 · pickier/pickier · GitHub
Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: pickier/pickier
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.1.64
Choose a base ref
...
head repository: pickier/pickier
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.1.65
Choose a head ref
  • 2 commits
  • 7 files changed
  • 1 contributor

Commits on Aug 23, 2026

  1. fix(no-unused-imports): do not read imports.push(…) as an import st…

    …atement
    
    The statement test was `/^\s*import\s*(?![(.])/`, which is happy with a line
    beginning `imports.push(…)` - `import`, then `\s*` matching nothing, then a
    lookahead that only rules out `(` and `.`. `imports` is exactly what a file that
    BUILDS import statements calls its accumulator.
    
    The damage is not a spurious binding. The scan then runs forward looking for a
    `from` clause that is not there, swallows dozens of real lines as "part of the
    import" and blanks them out of the searchable body, so every genuinely-used name
    below reads as unused. In one file that meant `componentsPath`, used twice
    inside those very template literals, reported as an unused import - and acting
    on that report deletes it.
    
    Same shape as the dynamic-`import()` bug this rule shipped with, one lookahead
    further on: `import` needs a word boundary, not just a check of what comes after
    the whitespace.
    
    Found by removing the 72 unused imports the rule reported across a real
    repository and letting the type checker referee: 70 were genuine and two broke
    the build, which is the only reason this was ever visible.
    chrisbbreuer committed Aug 23, 2026
    Configuration menu
    Copy the full SHA
    2291418 View commit details
    Browse the repository at this point in the history
  2. chore: release v0.1.65

    chrisbbreuer committed Aug 23, 2026
    Configuration menu
    Copy the full SHA
    7a6bad0 View commit details
    Browse the repository at this point in the history
Loading