Use dprint as the default formatter - #15
Merged
Merged
Conversation
SandroMaglione
marked this pull request as ready for review
August 2, 2026 09:49
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root cause
The repository did not provide a local dprint executable, root configuration, or workspace editor path on the current main branch. The editor extension therefore fell back to a globally installed
dprint, which was unavailable, and reported that no configuration file could be found.Impact
Contributors can run formatting through pnpm or save supported files in VS Code/Cursor and receive the same output as the Effect repository without installing dprint globally.
Validation
dprint checktsc -p tsconfig.json --noEmittsc -p tsconfig.build.jsonvitest run— 207 tests passed across 5 filesdprint.jsonis byte-identical toreferences/effect/dprint.json