Post

Released dprint 0.55—a pluggable and configurable code formatting platform that unifies all your formatters behind a single command. This substantial release lets you specify formatting plugins from npm.

Excited for npm resolution just because it means maybe I can not merge my PR that vendors all of the wasm blobs into the TS repo (I think a firewall is going to start denying the plugin domain) Hopefully the other plugins out there start publishing... I need to start publishing the dprint one there

Then again I don't really want to use the name @jakebailey/gofumpt for a plugin, so I guess I'll still call it @jakebailey/dprint-plugin-gofumpt

You could make the package multi-purpose maybe. I don't think there's a gofumpt formatter on npm. For example, place a plugin.wasm file for the dprint plugin, and then have an index.js with an api for formatting with gofumpt via that Wasm file in JavaScript.

Btw, of you specify any dependencies, dprint won't download them (only the initial package) because all it's interested in is the plugin.wasm file.

I could make it multipurpose but I have no clue who would need such a thing. @jakebailey/dprint-gofumpt is a possibility...

0 reposts0 likes

As for the npm resolution itself, I think I missed that you would have it pull from npm itself if a version is there; at least internally we have azdo package feeds that you configure in npmrc to not pull from the registry directly, so I'm not sure that'd work, but, a npm dep is probably enough

Yeah, when the version isn't there then it does node resolution and you only need to maintain the versions in a package.json When a version is specified, dprint will read the npmrc by default (I utilized some deno crates) so that should work, but let me know if not.