djlint.com

What It Is

djLint is a command-line linter and formatter for HTML templates. Its goal is to bring the kind of formatting and static-checking capabilities common in the Python and JavaScript ecosystems to templates such as Django, Jinja, Nunjucks, Twig, Handlebars, Mustache, Go templates, and Angular. It can be installed from PyPI or via Homebrew. npm installation is marked as experimental and requires Python and pip to already be available on the system.

Core Features and Ecosystem

In terms of functionality, djLint supports --lint for checking common template and HTML issues, --reformat for automatic formatting, and --check to preview differences first. It provides a large set of rules, including checks for HTML lang, DOCTYPE, attribute casing, img alt text, HTTPS external links, Django static/url usage, Jinja url_for, spacing around template variables, and more. Configuration can be placed in pyproject.toml, djlint.toml, .djlint.toml, or .djlintrc, with command-line arguments overriding configuration files.

For extensibility, it supports custom rules: you can write regex-based pattern rules or import a Python module and implement a run() function. Its integration ecosystem is fairly complete, covering pre-commit, SublimeText Linter, VS Code, Open VSX, neovim via none-ls/coc.nvim/efm-langserver, and MegaLinter.

Pricing and Deployment

The documentation explicitly describes it as a free cleaning service, with no mention of a commercial edition, subscription, or enterprise pricing. It is essentially a local CLI tool that can run on a developer machine, in CI, through pre-commit, or via editor plugins. It does not involve a SaaS account or payment flow. “Self-hosting” here does not mean deploying a service; it simply means installing and using it in your own environment.

Pros and Cons

Its strengths are broad template-language coverage, fine-grained configuration, extensible rules, and natural integration into development workflows. For server-rendered projects such as Django or Jinja applications, it can significantly improve consistency across template code. The limitations are also clear: the documentation states that formatting is still in beta and recommends using --check first; djLint is not an HTML parser or syntax validator; long JSON/HTML data embedded in attributes cannot be reformatted, and template syntax inside style/script blocks is not fully supported.

Who It’s For and Access from China

It is a good fit for teams maintaining large numbers of HTML templates who want to standardize formatting and catch basic issues before commits, especially Python web projects, static sites, and repositories that mix multiple template engines. As for access from China, the documentation does not provide information on network availability, mirrors, or payments. Actual usability of PyPI, GitHub, VS Marketplace, and related services will depend on the local network environment, so the conclusion can only be marked as unknown. The documentation does not list comparable alternatives.