dprint VS core_d.js

Prettier is opinionated. dprint is highly configurable.

I mean, I know I am a bad person because of those long names, but that is how life goes sometimes! And the blank line there at the top is just very important to like, catch one's breath, while reading this code.

(I'm really just posting this in the hopes that somebody will throw me a "Bro, just use hpstrlnt, it totally lets you configure that!" -- I have not actually tried Rome to see if it does (it's Monday morning and I'm not quite ready to be disappointed again...))

[1]: dprint is good, and I recommend it as the best code formatter I currently know of: https://dprint.dev/

If it's something in the vein of one of those things then, worst case, you generate the code first, then run it through something like dprint.

If it's speed you are looking for, give dprint (https://github.com/dprint/dprint) a try, it has a vscode plugin too.

Why not dprint[1]? Does it not "produce a concrete syntax tree (CST) that represents the original code completely, whitespace, comments and all"?

I'm not terribly familiar with the architecture of dprint, but it's used in Deno with JS/TS plugin and works great so far.

[1] https://github.com/dprint/dprint

It is written in Rust, and the formatting is built into the Deno executable using a clone of Prettier https://dprint.dev/. You can use it as your main language server for web based JS/TS as well as Deno specific code.

dprint is 99% the same as Prettier, I suggest you try it out and look at the diffs. I did, and reported any differences on https://github.com/dprint/dprint ... any differences all got fixed :)

Yeah! And if we ever have the need to have another tool in the list of daemonized tools, we can do it using this: https://github.com/mantoni/core_d.js (as the author of prettierd documented). I find the approach very interesting!