Skip to content

Use dprint as the default formatter - #15

Merged
SandroMaglione merged 1 commit into
mainfrom
agent/fix-dprint-vscode
Aug 2, 2026
Merged

Use dprint as the default formatter#15
SandroMaglione merged 1 commit into
mainfrom
agent/fix-dprint-vscode

Conversation

@SandroMaglione

Copy link
Copy Markdown
Member

Summary

  • replace Prettier with dprint and use the same pinned formatter configuration as Effect
  • add the local dprint dependency and update the formatting scripts
  • configure VS Code/Cursor to use the workspace dprint executable on save
  • recommend the dprint editor extension and normalize the existing supported files
  • make incomplete README TypeScript fragments formatter-stable

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 check
  • tsc -p tsconfig.json --noEmit
  • tsc -p tsconfig.build.json
  • vitest run — 207 tests passed across 5 files
  • confirmed dprint.json is byte-identical to references/effect/dprint.json

@SandroMaglione
SandroMaglione marked this pull request as ready for review August 2, 2026 09:49
@SandroMaglione
SandroMaglione merged commit e690c05 into main Aug 2, 2026
2 checks passed
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