plugins.dprint.dev

Website for https://plugins.dprint.dev.

URLs to Any GitHub Repo (For Plugin Authors)

This service provides a convenient URL for a plugin stored in any GitHub repo.

To use it, create a GitHub release in your repo with:

1. Plugin named plugin.wasm (use plugin.json for process plugins)
2. JSON schema named schema.json (if exists)

Then your URLs will look like:

https://plugins.dprint.dev/<username>/<repo_name>-<tag_name>.wasm
https://plugins.dprint.dev/<username>/<repo_name>/<tag_name>/schema.json
https://plugins.dprint.dev/<username>/<repo_name>/latest.json

Restrictions and recommendations:

1. Tag names must not contain a dash (-).
2. It is recommended to use the format x.x.x for your tag names to be consistent with other plugins (ex. no leading v like v1.0.0).

If your repo name is in the format dprint-plugin-<something> then you can omit dprint-plugin- in the <repo_name> for the URL (ex. https://plugins.dprint.dev/<user>/dprint-plugin-typescript-0.0.0.wasm may be shortened to https://plugins.dprint.dev/<user>/typescript-0.0.0.wasm).

Note that once a URL is cached it is cached forever by the service.

Release Assets

For approved repositories, individual release assets can be served directly via:

https://plugins.dprint.dev/<username>/<repo_name>/<tag_name>/asset/<asset_name>

For example:

https://plugins.dprint.dev/dprint/dprint-plugin-prettier/0.67.0/asset/dprint-plugin-prettier-aarch64-apple-darwin.zip

This is useful for process plugins that distribute platform-specific binaries (unfortunately this bug prevents using relative URLs for some time). Assets are cached in R2 for persistence.

Note: To get approved, open a PR to this repository including your username and plugin repo.

Run Locally

npm install
npm run dev