Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feature: structural diffs (diff ASTs rather than text)

Open
#780 2 comments 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
devtools

Research direction

The issue does not name files, tests, or an implementation entry point; start by reading the contributing guidelines and locating Pierre’s existing diff pipeline. Done means structural diffs compare syntax trees rather than raw text and make formatting-only changes less noisy, as described in the proposal.

Written by the indexing model from the issue text.

Description

diffs enhancement
Prerequisites
Proposal

I'm a big fan of structural highlighting as seen in tools like difftastic and Linear Diffs. I would like to propose bringing this feature to Pierre Diffs.

Motivation and context

Formatting changes add a lot of noise to diffs. This can be partially mitigated by configuring the diff to ignore whitespace (e.g. git diff -w) or perform a word diff (e.g. git diff --word-diff), but we can achieve even better results with a "structural diff" that performs a diff on ASTs rather than text. See https://difftastic.wilfred.me.uk/introduction.html#syntactic-diffing.

Personally, after using difftastic for a few months, I really struggle to go back. There's a huge difference in diff readability.

Dominant language
TypeScript
Stars
6.2k
Forks
226
Avg merge
1d 12h
Merged PRs (30d)
34

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pierrecomputer/pierre

All issues in pierrecomputer/pierre

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.