Skip to content

Drop the polyfill for the engine's findConfigDirs - #19

Draft
grouville wants to merge 1 commit into
dagger:mainfrom
grouville:polyfill-removal
Draft

Drop the polyfill for the engine's findConfigDirs#19
grouville wants to merge 1 commit into
dagger:mainfrom
grouville:polyfill-removal

Conversation

@grouville

@grouville grouville commented Aug 7, 2026

Copy link
Copy Markdown
Member

The Vitest module currently uses dagger/polyfill to find projects below the directory where Dagger was run, or the nearest project above it when invoked from a subdirectory.

That exact behavior is now available as Workspace.findConfigDirs in dagger/dagger#13854. This PR switches the discovery call and removes the wrapper. Vitest arguments, execution, and result handling do not change.

Test

dagger check

All 6 checks pass, including ancestor and descendant discovery and fixtures with expected test failures. The provisional engine version will be updated after #13854 is released.

The engine now ships Workspace.findConfigDirs (dagger/dagger#13769):
the same cwd-aware project discovery this module got from
github.com/dagger/polyfill — same semantics, ported from the
polyfill's own design and test matrix. Swap the call, drop the
dependency, and require the engine release that ships it.

The engineVersion bump and the dependency removal have to land
together: the version gate is what keeps the engine's new changeset
behavior scoped to migrated modules.

Signed-off-by: Guillaume de Rouville <guillaume@dagger.io>
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