@kjanat/svg-toolkit
Every svg-toolkit CLI in one install:
npm install -g @kjanat/svg-toolkit
puts svg-language-server (alias svg-ls), svg-lint, and svg-format on
your PATH, via exact-pinned dependencies on the individual packages.
Why not just svg-toolkit?
Because npm. The unscoped name svg-toolkit has been squatted since 2019 by an
abandoned "base 3d" package, and npm's name police block anything that even
smells like an existing name — which is also why there is no unscoped svg-lint
(npm considers it "too similar" to svglint; fucking great, thanks npm). So:
scoped it is.
Prefer the individual tools?
| LSP server | svg-language-server | @svg-toolkit/svg-language-server |
| Linter | — (blocked by npm) | @svg-toolkit/svg-lint |
| Formatter | svg-format | @svg-toolkit/svg-format |
Each resolves a prebuilt native binary for your platform via
optionalDependencies on @svg-toolkit/* platform packages — no postinstall
step, no install-time network access outside npm.
Docs: https://github.com/kjanat/svg#readme