Skip to content

fix: isolate exported-name caches between runs - #7

Open
everton-dgn wants to merge 1 commit into
webpro-nl:mainfrom
everton-dgn:fix/isolate-export-cache-between-runs
Open

everton-dgn wants to merge 1 commit into
webpro-nl:mainfrom
everton-dgn:fix/isolate-export-cache-between-runs

Conversation

@everton-dgn

Copy link
Copy Markdown

Calling unbarrelify again after changing a source file can reuse its old exported names. A dry-run followed by a write can then point an import at a file that no longer exports that name.

Keep the export cache in the context of each run. Barrels within one run still share it, while separate and overlapping calls use independent caches. The regressions exercise both discovery and explicit-barrel modes, then execute the rewritten consumers.

All 185 tests, build, lint, formatting and installed-check passed on Node 24. The four new cases fail against the base.

Calling unbarrelify again after changing a source file can reuse its old exported names. A dry-run followed by a write can then point an import at a file that no longer exports that name.

Keep the export cache in the context of each run. Barrels within one run still share it, while separate and overlapping calls use independent caches. The regressions exercise both discovery and explicit-barrel modes, then execute the rewritten consumers.

All 185 tests, build, lint, formatting and installed-check passed on Node 24. The four new cases fail against the base.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant