Skip to content

bump dprint to 2025 + relax operatorPosition#24

Merged
johncarmack1984 merged 1 commit into
mainfrom
john/dprint-2025
May 6, 2026
Merged

bump dprint to 2025 + relax operatorPosition#24
johncarmack1984 merged 1 commit into
mainfrom
john/dprint-2025

Conversation

@johncarmack1984

Copy link
Copy Markdown

Summary

  • dprint CLI: 0.50.2 -> 0.54.0
  • dprint-plugin-typescript: 0.85.1 -> 0.96.0
  • dprint-plugin-json: 0.17.4 -> 0.21.3
  • dprint-plugin-markdown: 0.15.3 -> 0.21.1
  • dprint-plugin-exec: 0.4.3 -> 0.6.2
  • Config: binaryExpression/conditionalExpression/conditionalType.operatorPosition set to maintain

dprint fmt is a no-op on main after the bump -- no existing source files reformat. The operatorPosition: maintain change makes dprint accept multi-line &&/||/ternary either at end-of-line or start-of-next-line, instead of forcing one. That removes a category of "works locally, fails CI" drift for external contributors.

Effect on #22 after rebase

Of the 3 files #22 currently fails dprint check on:

File Status after this PR
example/src/lib/testing.ts passes (was a && operator-position drift; now accepted by maintain)
taurpc/src/export.rs unchanged -- this is rustfmt --edition 2024 let-chain layout drift, decided by which rustfmt is on PATH (CI's vs Oscar's). A rust-toolchain.toml pin in a follow-up would deterministically fix this category
README.md unchanged -- example code in TS code fences uses "double" quotes; repo quoteStyle is preferSingle. Stylistic inconsistency in the contributed content. Either Oscar adjusts in his branch (small fix), or a follow-up adds <!-- dprint-ignore --> around the affected fences after rebase

So: this PR unblocks one of the three drifted files. The other two are content/toolchain decisions, not config.

Test plan

  • pnpm install clean
  • pnpm lint clean (types + format + js)
  • dprint fmt produces zero diff on main
  • Synthetic version of #22's testing.ts &&-style passes dprint check with new config

@johncarmack1984 johncarmack1984 merged commit a0b7c5b into main May 6, 2026
1 check 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