Loading video...
Video Failed to Load
a jev lint rule that detects if a new component is a potential duplicate of an existing file. this check takes less than a second + costs less than $0.01 (for our codebase at least) jev makes it feel actually reasonable to run these checks on every code change.
11,509 views • 13 days ago •via X (Twitter)
10 Comments

Wilco Kruijer13 days ago
There's 50 years of research on finding "code clones", you do not need Jev for this

unhinged faces13 days ago
Do this but for methods/functions/classes next.

Sebastian Hindhede13 days ago
This requires some consideration to the short context window, but goddamn this is cool application of jev!

Rida F’kih13 days ago
Tree-sitter AST + embedding models have been a great tool for this

Alek13 days ago
Teddy - does this run pre-commit or in CI?

Brjan | AI Builder13 days ago
how often do you find actual duplicates after running that check?

hacsceo13 days ago
Why may at all? Get it Free Locally and most importantly PRIVATE. Zero API cost, Full ownership

Zach Lee13 days ago
@daltonc One of the best use cases I’ve seen.

EJ Campbell13 days ago
@grok how many lines of code can Jev hold?

Salise13 days ago
running checks on every code change sounds super efficient, especially for just $0.01 per check

