git404hub

what is datastar-lint fr?

calionauta/datastar-lint — explained in plain English

Analysis updated 2026-05-18

1GoAudience · developerComplexity · 2/5Setup · easy

tl;dr

A command line linter that catches Datastar attribute typos and backend SDK mistakes across HTML, Go, Python, and TypeScript before they fail at runtime.

vibe map

mindmap
  root((datastar-lint))
    What it does
      Lints HTML data attrs
      Lints backend SDK calls
      Catches runtime-only bugs
    Tech stack
      Go
      Python
      TypeScript
    Use cases
      Run in CI
      Catch typos early
      Config custom attrs
    Audience
      Datastar developers
      Web app teams

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Catch data attribute typos before they silently fail in the browser.

VIBE 2

Verify Go, Python, or TypeScript backend code sends valid Datastar selectors.

VIBE 3

Run the linter in CI to fail a build when Datastar mistakes are found.

VIBE 4

Allow intentional custom data attributes through a config file while still flagging real typos.

what's the stack?

GoPythonTypeScriptHTML

how it stacks up fr

calionauta/datastar-lintadvayc/wrappedaegrail/aegrail-engine
Stars111
LanguageGoGoGo
Setup difficultyeasyeasyhard
Complexity2/52/55/5
Audiencedevelopergeneralops devops

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 5min

Installing requires Go 1.26 or newer even though the tool can lint non-Go projects too.

in plain english

datastar-lint is a command line tool that checks projects using Datastar, a library for building interactive web pages, for mistakes that would normally only show up later, in the browser or over a live connection to the server. Datastar works through special data attributes placed on HTML elements and matching function calls in backend code, and this tool looks at both sides at once, across Go, Python, and TypeScript projects. The problem it solves is that many Datastar mistakes compile and build without any error. A misspelled attribute like data on clik is silently ignored by the browser. Calling a backend function to patch elements without telling it which part of the page to target throws an error only when the page actually runs. A formatting mismatch in a Go function call is not caught by the Go compiler. Sending an empty update can quietly wipe out all of an application's stored state. This tool moves all of these problems from something discovered after the app is running to something caught automatically before that, in a continuous integration pipeline. It installs as a single Go binary and requires Go version 1.26 or newer to install, though using it does not require every project to be written in Go. Once installed, it can check HTML, Templ, TSX, JSX, and plain JavaScript or TypeScript files for attribute mistakes by default, and can additionally be told to inspect Go, Python, or TypeScript backend code for its own set of checks specific to that language's Datastar calls. Running it against a folder produces a list of warnings or errors and returns a simple pass or fail result that other tools, like a build pipeline, can act on. Projects that intentionally use custom data attributes that are not part of Datastar can list them in a small configuration file so the linter stops flagging them, while genuine typos are still reported with a suggested correction. The tool also quietly checks in the background whether a newer version of itself is available and can update itself when asked.

prompts (copy fr)

prompt 1
Show me how to install datastar-lint and run it against my project's HTML and Go files.
prompt 2
Explain what PATCH_ELEMENTS_NO_SELECTOR means and how to fix it.
prompt 3
How do I add my custom data-* attributes to a .datastar-lint.yaml config file?
prompt 4
Walk me through wiring datastar-lint into a CI pipeline so failing checks block a merge.

Frequently asked questions

what is datastar-lint fr?

A command line linter that catches Datastar attribute typos and backend SDK mistakes across HTML, Go, Python, and TypeScript before they fail at runtime.

What language is datastar-lint written in?

Mainly Go. The stack also includes Go, Python, TypeScript.

How hard is datastar-lint to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is datastar-lint for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.