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

suggestion: diffity-server

Open
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Review the repository's current application startup and UI entry points to understand how projects, diff ranges, and trees are opened today. Define the server mode's scope around a persistent process, a lightweight UI or command bar, and switching between projects; the issue is done when this design is agreed and a working prototype meets those use cases.

Written by the indexing model from the issue text.

Description

i like a lot of the functionality diffity offers, i tried vibing something similar at some point, with a slightly different take

i've been anchored at my vscode/cursor ui mainly as a dumb filebrowser/gitbrowser, its especially convenient because code-server is viable as a web app when working remotely from different machines over tailscale

could there be a mode for diffity to act as a permanent long-living server on a machine? kind of like code-server?

Where i could have a light ui / command bar to open different projects / diff ranges / trees all within a single always-on server on the machine.

is the diffity project interested in doing such a thing? does this sound like a good idea? or was this perhaps already considered but intentionally left out for reasons like perf issues or other reasons?

Let me know if I should try prototyping this while keeping in mind it could be accepted as a PR, or if i should consider making a separate version for myself without any consideration for opening a PR.

Any notes if this was already thought of would be appreciated.

Dominant language
TypeScript
Stars
775
Forks
57
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 nilbuild/diffity

All issues in nilbuild/diffity

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.