wasm-git

GIT for nodejs and the browser using https://libgit2.org compiled to WebAssembly with https://emscripten.org

Web Development Developer Tools

Explore on GitHub Read Hacker News discussions

3Distinct people

5Mentions

0Explicit recommenders

851GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

GIT for nodejs and the browser using https://libgit2.org compiled to WebAssembly with https://emscripten.org

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year5 dated mentions

Observed mentions: 2020-02-26 08:04:25 UTC to 2025-03-06 02:25:20 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	4	2	2
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	0	0	0
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	0	0	0
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	1	0	1

What Hacker News says

5 sources

mikepurvis·Mar 6, 2025

That does get intense pretty quickly, if you're generating a source and commit/diff pages for every file * every commit. Probably just single commits would make the most sense and then a source browser for each branch. That said, JavaScript libgit2 is a thing [1], so doing it "properly" in a client app is totally possible. [1]: https://github.com/libgit2/libgit2/issues/4376 | https://github.com/petersalomonsen/wasm-git

In Git without a forge

k__·Mar 2, 2020Submission

Git for Node.js and the browser compiled to WebAssembly

3 points · Open discussion

mstade·Feb 26, 2020

Actually, looks like emscripten has support for a few different options, including IndexedDB[1]. I have a use case where we'd like to both use the local filesystem via Node APIs as well as in-memory in the browser. I asked the author of wasm-git and it looks like this is possible with a custom build[2]. [1]: https://emscripten.org/docs/api_reference/Filesystem-API.htm... [2]: https://github.com/petersalomonsen/wasm-git/issues/3

In Git for Node.js and the browser using libgit2 compiled to WebAssembly

mstade·Feb 26, 2020Submission

Git for Node.js and the browser using libgit2 compiled to WebAssembly

16 points · Open discussion

mstade·Feb 26, 2020

I wonder how this compares to wasm-git[1], which is libgit2 compiled to wasm for use in both the browser and node. At face value it seems isomorphic-git has been around for longer, and wasm-git seems hot off the press, but the latter seems like maybe it's got more eyes on the prize given libgit2's developer base? (I have no affiliation with either project, just looking for options to use git in-browser and in node.) [1]: https://github.com/petersalomonsen/wasm-git

In Isomorphic-git v1.0