chore(deps): update ⬆️ mise-packages - #965

v0.55.1

Compare Source

Changes

• fix(npm): resolve node_modules from config dir
  (#​1194)

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

v0.55.0

Compare Source

dprint is a pluggable and configurable code formatting platform that unifies all your formatters.

This substantial release adds npm specifier plugins, brings dprint to many more CPU architectures, adds richer LSP support, and gives you finer-grained configuration with per-file overrides and config inheritance.

It includes two behaviour changes worth reading before you upgrade.

Highlights

• 📦 npm specifier plugins — reference plugins with npm:@​scope/name@version
• 🏗️ Runs on many more architectures — Windows on ARM, Android (Termux), ppc64le, and LoongArch
• 💡 LSP completions & hover for dprint configuration files
• 🔀 dprint fmt --dirty — format only the files with uncommitted git changes
• 🎛️ Per-file plugin config overrides — apply different plugin options to specific files
• 🧬 "inherit": true for nested configuration files
• ⚠️ Plugin associations are now additive (behaviour change)
• ⚠️ Globs are now case-sensitive (behaviour change)

There's also a new website: https://dprint.dev

npm specifier plugins

You can now reference plugins via an npm: specifier in your config:

{
  "plugins": [
    "npm:@​dprint/typescript@0.95.15",
    "npm:@​dprint/json"
  ]
}

• Pinned form (npm:@​scope/name@version) downloads and locks an exact version.
• Omitting the version (npm:@​scope/name) resolves the plugin from node_modules, walking up from the config file so npm and your lockfile stay the source of truth.
• dprint add npm:@​scope/name resolves the latest version and writes the pinned form, unless the package is in a nearby package.json under devDependencies, in which case the unversioned form is written, in which case node resolution will occur.

More architectures supported

dprint now runs on a much wider range of CPU architectures, including:

• Windows on ARM (aarch64-pc-windows-msvc) - Now native—previously dprint was shipping the x64 binary.
• Android / Termux.
• ppc64le.
• LoongArch (now able to run plugins).

This is made possible by migrating the Wasm plugin runtime from Wasmer to Wasmtime, with equivalent performance and a smaller dependency tree:

• Native Cranelift codegen on x86_64, aarch64, riscv64, and s390x.
• ppc64le, LoongArch, and Android compile to Wasmtime's portable Pulley bytecode (pure Rust, no native backend, no signal-based traps — which the Android sandbox doesn't allow), replacing the previous wasmi interpreter path.

LSP completions and hover for config files

dprint lsp now provides autocompletion and hover documentation when editing dprint.json / dprint.jsonc, making it easier to discover plugins and configuration options without leaving your editor.

dprint fmt --dirty

Format only the files with uncommitted changes in your git working directory — staged, unstaged, and untracked (but not gitignored):

dprint fmt --dirty

This complements the existing --staged flag.

"inherit": true for nested config files

A nested configuration file can now opt in to inheriting its ancestor's plugins and configuration. Given a config at the repo root:

// ./dprint.json
{
  "typescript": {
    "indentWidth": 4
  },
  "plugins": [
    "https://plugins.dprint.dev/typescript-0.96.1.wasm"
  ]
}

A config in a subdirectory can inherit it with "inherit": true:

// ./sub-project/dprint.json
{
  "inherit": true,
  "typescript": {
    // inherits the ancestor's TypeScript config, but overrides the indent width
    "indentWidth": 2
  }
}

• Plugins in the nested config take precedence; any not specified are inherited.
• The ancestor's includes are not inherited.
• Inheriting is opt-in so that adding a config higher in the tree doesn't unexpectedly start affecting nested configs.

Per-file plugin config overrides

Plugins now support "overrides" blocks to apply different configuration to specific files:

{
  "json": {
    "overrides": {
      "files": ["**/package.json", "**/composer.json"],
      "indentWidth": 4
    }
  }
}

Use an array for multiple overrides:

{
  "json": {
    "overrides": [
      {
        "files": ["**/package.json", "**/composer.json"],
        "indentWidth": 4
      },
      {
        "files": "**/special-package.json",
        "lineWidth": 80
      }
    ]
  }
}

Overrides are honoured consistently across CLI formatting, stdin, the editor service, the LSP, and host formatting. Note that overrides only change configuration — they don't include or exclude files.

⚠️ Plugin associations are now additive (behaviour change)

Previously, adding an "associations" glob to a plugin silently replaced the file extensions and file names it matched by default. Now associations are additive:

• A positive glob (e.g. **/*.foo) routes extra files to the plugin while its defaults keep matching.
• A negated glob (e.g. !**/*.js) cancels a default extension, file name, or path.

If you previously relied on a positive association to replace the defaults, add a negated glob to opt back out. Fixes the surprising behaviour in #​841 and #​794.

⚠️ Globs are now case-sensitive (behaviour change)

File pattern matching for includes/excludes globs is now case-sensitive (#​1082). If your patterns relied on case-insensitive matching, update them to match the actual file casing.

Read a list of files from stdin

The new --stdin-files flag reads a newline-separated list of file paths from stdin instead of from the command line arguments. It works with the fmt, check, file-paths, and format-times subcommands, which is handy when piping the output of another tool into dprint:

generate_files | dprint fmt --stdin-files

Smarter dprint init

dprint init now scans the current directory and pre-selects the plugins whose files it finds, so the defaults match your project out of the box. The plugin picker scrolls to fit your terminal and supports type-to-filter, keeping it usable even when many plugins are available.

Pass --yes (-y) to skip the prompt entirely and accept those defaults — handy for scripts and CI:

dprint init --yes

The prompt is also skipped automatically when there's no interactive terminal.

Other notable additions

• DPRINT_GLOBAL_GITIGNORE=1 — opt in to respecting git's global excludes file (core.excludesFile). Opt-in because it's machine-specific and won't exist on CI.
• NO_COLOR / FORCE_COLOR support for controlling colored output.
• dprint config update --dry-run — preview config updates without writing.
• dprint resolved-config --file <path> — show only the plugins that would format a given file.
• dprint incremental-state — print the exact signal dprint uses to decide cache reuse, so you can diff it between revisions.
• Shorter subcommand names — output-resolved-config, output-file-paths, and output-format-times are now resolved-config, file-paths, and format-times.

Changelog

Features

• feat(BREAKING): make plugin associations additive to default file matching (#​1172)
• feat(BREAKING): make globs case sensitive (#​1089)
• feat: migrate wasm plugin runtime from wasmer to wasmtime (#​1178)
• feat: add Windows on ARM (aarch64-pc-windows-msvc) builds (#​1179)
• feat: add android (Termux) builds using the wasmi interpreter backend (#​1175)
• feat: add ppc64le builds using the wasmi interpreter backend (#​1174)
• feat: use LLVM backend for LoongArch to support plugins (#​1109)
• feat: LSP completions and hover for dprint configuration files (#​1177)
• feat: support resolving plugins via npm specifiers and node resolution (#​1134)
• feat: add --dirty flag to format git working directory changes (#​1171)
• feat: add per-file plugin config overrides (#​1136)
• feat: support "inherit": true in nested configuration files (#​1160)
• feat: opt-in support for git's global excludes file via DPRINT_GLOBAL_GITIGNORE (#​1163)
• feat: support reading a list of files to format from stdin (#​1157)
• feat: support NO_COLOR and FORCE_COLOR env vars (#​1155)
• feat: add --dry-run to dprint config update (#​1156)
• feat: add --file flag to resolved-config to filter plugins by file (#​1167)
• feat: add dprint incremental-state command (#​1149)
• feat: drop output- from some subcommands (#​1150)
• feat(npm): detect plugin kind on dprint add when no path is given (#​1183)
• feat(npm): add --checksum flag to dprint add (#​1184)
• feat(init): pre-select plugins from the current directory, scrollable/filterable picker, and --yes flag (#​1185)
• feat(init): scaffold plugin config from info.json (defaultConfig + configItems) (#​1186)
• feat(init): prioritize plugin pre-selection and surface it in the list
  (#​1187)

Performance

• perf: reduce wasm plugin thread stack size to 4 MiB (#​1180)
• perf: read directories on multiple threads when globbing (#​1168)
• perf(windows): delay load DLLs not needed at startup (#​1164)
• perf: cache resolved global gitignore path to avoid repeated git subprocess (#​1165)
• perf: use similar for LSP diffing and drop dissimilar (#​1176)

Bug Fixes

• fix: normalize LSP formatted line endings to match the editor document (#​1173)
• fix: avoid hang waiting for killed process plugins in clear-cache (#​1169)
• fix: kill process plugins when running dprint clear-cache (#​1154)
• fix(npm): download binary when optional dependency is omitted (#​1161)
• fix(npm): improve musl detection (#​1145)
• fix: recompile Wasm plugin from source when loading from cache fails (#​1158)
• fix: avoid regex size limit when given many literal file paths (#​1153)
• fix: read .git/info/exclude when respecting gitignore (#​1151)
• fix(plugins): surface plugin cache cleanup errors instead of swallowing them (#​1148)
• fix(core): prevent unbounded re-evaluation when conditions oscillate (#​1137)
• fix: include plugin's resolved config in incremental cache key (#​1138)
• fix(install.sh): correct riscv64 build name, add loongarch64 support, Windows .exe path, resolve relative DPRINT_INSTALL (#​1131)

Internal

• refactor: redesign plugin cache as flat per-plugin sidecars (#​1181)

Install

Run dprint upgrade or see https://dprint.dev/install/

Checksums

v2.65.2

Compare Source

Changes:

• Memory usage calculations now exclude the ZFS ARC cache on Linux, FreeBSD, NetBSD, and SunOS. (#​1995 / #​2418, Memory)
  • This prevents the Memory module from reporting artificially high memory usage on systems with the ZFS kmod enabled.

Bugfixes:

• The GPU module no longer pings sleeping dedicated GPUs on dual-GPU laptops. (#​2419, GPU)
  • As a result, PCIe link speed detection (introduced in v2.65.0) is now only enabled in driverSpecific mode.
• Fixed a crash when detecting hardware codec support with the amdgpu driver on Linux. (#​2419, Codec, Linux)

Logos:

• Updated CachyOS_small
• Added Turkish

v0.3.1

Compare Source

Features

#​475 Support copying the device flow one-time code to the clipboard on ghtkn auth

ghtkn auth can copy the one-time code to the system clipboard for you.
This is only available on ghtkn auth, the explicit, interactive authentication command - not on ghtkn get or ghtkn git-credential, which must not start the device flow on your behalf.
It is disabled by default; enable it with the -clipboard (-p) flag, the GHTKN_CLIPBOARD environment variable, or the clipboard.enable config field.

ghtkn auth -p

export GHTKN_CLIPBOARD=true

clipboard:
  enable: true

$ ghtkn auth -p
The application uses the device flow to generate your GitHub User Access Token.
Copy your one-time code: 0000-0000
(The one-time code has been copied to your clipboard.) <= New!
...

[!WARNING]
When pasting the code from the clipboard into the web form, please verify that it matches the one displayed in the output.

Note that this feature doesn't work in some environments such as containers.

foo@c4f18eb0cebe:~/workspace$ GHTKN_BACKEND=text ghtkn auth
initialize the clipboard: clipboard unavailable: Failed to connect to the X11 display, so the clipboard
package will not work properly. Make sure an X server is running and the
DISPLAY environment variable is set.

If the clipboard package runs in an environment without a frame buffer,
such as a cloud server, it may be necessary to install xvfb:

	apt install -y xvfb

and initialize a virtual frame buffer:

	Xvfb :99 -screen 0 1024x768x24 > /dev/null 2>&1 &
	export DISPLAY=:99.0

Then this package should be ready to use.

Jun 28 04:53:57.549 WRN Failed to copy the one-time code to the clipboard automatically. Please copy it manually program=ghtkn version="" app_name=szksh-lab-2/none
The application uses the device flow to generate your GitHub User Access Token.

v0.3.0

Compare Source

⚠️ Breaking Changes

#​477 Disable the automatic device flow by default

Part of #​474, phase 1 of the rollout.

ghtkn get, ghtkn git-credential, and SDK don't start the device flow automatically by default anymore.
You need to run ghtkn auth explicitly to start the device flow.
This reduces the risk of device code phishing.

If you prefer the previous behavior, you can still export GHTKN_ENABLE_DEVICE_FLOW=true and ghtkn get's -d option.
But at v0.4.0, these options will be removed.

Features

#​469 Add ghtkn revoke --all to revoke every app's stored token

ghtkn revoke --all

This is useful for the incident response.
When the environment running ghtkn is compromised, you can revoke all stored tokens immediately.

#​471 Support min_expiration in the config file
#​472 Support backend.type in the config file

min_expiration: 1h
backend:
  type: agent # One of agent, keyring, and text

Documentation

#​473 Host the config JSON Schema in this repository

https://github.com/suzuki-shunsuke/ghtkn/blob/main/json-schema/ghtkn.json

[!IMPORTANT]
Please modify the URL in the configuration file.
Before:

# yaml-language-server: $schema=https://raw.githubusercontent.com/suzuki-shunsuke/ghtkn-go-sdk/refs/head/main/json-schema/ghtkn.json

After:

# yaml-language-server: $schema=https://raw.githubusercontent.com/suzuki-shunsuke/ghtkn/main/json-schema/ghtkn.json

v3.9.3

Compare Source

v3.9.2

Compare Source

v1.1.131

Compare Source

v1.1.130

Compare Source