Add npm packages to info.json and latest.json - #71
Merged
Conversation
Each plugin published to npm now declares its package, which the dprint CLI uses to write an npm specifier into config files instead of a url. Verified for each package that it resolves on the registry, that its tarball contains the plugin.wasm/plugin.json the CLI resolves out of it, and that its latest version matches the plugin's latest GitHub release. No package exists for jolars/panache or drluckyspin/swift. latest.json serves the same property, mapped from info.json rather than duplicated.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
dprint-plugins | 59615e8 | Commit Preview URL Branch Preview URL |
Aug 05 2026, 02:31 PM |
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
1 participant
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.
Declares the npm package each plugin is published to, so the dprint CLI writes an npm specifier into config files instead of an https url.
info.json
"npm": { "name": ... }added to 21 of the 23 entries:dprint-plugin-*entries@dprint/typescript,@dprint/json,@dprint/markdown,@dprint/toml,@dprint/dockerfile,@dprint/biome,@dprint/oxc,@dprint/mago,@dprint/ruff,@dprint/jupyter,@dprint/prettier,@dprint/roslyn,@dprint/execjakebailey/gofumpt@jakebailey/dprint-plugin-gofumptg-plane/malvadprint-plugin-malvag-plane/markup_fmtdprint-plugin-markupg-plane/pretty_yamldprint-plugin-yamlg-plane/pretty_graphqldprint-plugin-graphqlbartlomieju/lax-css/lax-markup/lax-sqllax-css/lax-markup/lax-sqlNo npm package exists for
jolars/panacheordrluckyspin/swift, so those are unchanged.For each package I checked that it resolves on the registry, that its tarball contains the
package/plugin.wasm(orpackage/plugin.jsonfor the process plugins prettier/roslyn/exec) thatPluginNpmInfo::resolve_latestlooks for, and that its latest version matches the plugin's latest GitHub release. That ruled out two near-misses:malvaon npm is g-plane's standalone wasm build (standalone_wasm_bg.wasm, no plugin file), andpanacheis an unrelated package unpublished since 2011.latest.json
tryResolveLatestJsonnow serves the samenpmproperty. The mapping is derived frominfo.jsonrather than duplicated, keyed byusername/repoaftergetFullRepoNameresolution, with both the prefixed and unprefixed repo name registered so/dprint/typescript/latest.jsonand/dprint/dprint-plugin-typescript/latest.jsonboth hit.tsc --noEmitanddprint checkare clean. Note that the live-GitHub tests (including theg-plane/malvacase added here) can't run locally without a GitHub token — they 401 onmaintoo — so those are unverified outside CI.