EWewuhic·Oct 5, 2025Submission
ZetaOffice – WASM LibreOffice in the Browser
5 points · Open discussionallotropia
zetajs
JavaScript2024–2025
allotropia / zetajs
zetajs
JS wrapper for ZetaOffice in the browser
5Distinct people
8Mentions
0Explicit recommenders
230GitHub stars
What to know before exploring
What it is
JS wrapper for ZetaOffice in the browser
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, 5:04:57 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 month8 dated mentions
Observed mentions: 2024-11-08 14:43:13 UTC to 2025-10-05 21:05:06 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
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Nov 2024 | 2024-11-01 00:00:00 UTC | 2024-12-01 00:00:00 UTC | 5 | 1 | 4 |
| Dec 2024 | 2024-12-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| Jan 2025 | 2025-01-01 00:00:00 UTC | 2025-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2025 | 2025-02-01 00:00:00 UTC | 2025-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2025 | 2025-03-01 00:00:00 UTC | 2025-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2025 | 2025-04-01 00:00:00 UTC | 2025-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2025 | 2025-05-01 00:00:00 UTC | 2025-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2025 | 2025-06-01 00:00:00 UTC | 2025-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2025 | 2025-07-01 00:00:00 UTC | 2025-08-01 00:00:00 UTC | 1 | 0 | 1 |
| Aug 2025 | 2025-08-01 00:00:00 UTC | 2025-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2025 | 2025-09-01 00:00:00 UTC | 2025-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2025 | 2025-10-01 00:00:00 UTC | 2025-11-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
8 sourcesAnother example of Wasm in the browser is: ZetaOffice, which is LibreOffice in the Browser [1]. They recently joined Collabora, which is used for example in OpenDesk[2], which is a replacement for Office365.
ZetaOffice talk[3] about the challenges porting Libreoffice to run client-side in the browser. With topics like GUI Event Handling, Debugging or Multi-Threading, File- System & Size to topics such as CI/CD and dependency handling and upstream.
[1] https://github.com/allotropia/zetajs / https://zetaoffice.net/
[2] https://www.opendesk.eu/en
[3] https://media.ccc.de/v/clt23-249-libreoffice-technology-and-...
In WebAssembly: Yes, but for What?This demo is read only.
https://zetaoffice.net/demo2.html
https://github.com/allotropia/zetajs/tree/4e071799d6318ac683...
In ZetaOffice: LibreOffice in the BrowserBeing one of the ZetaOffice (and LibreOffice) hackers, I use Firefox as my primary browser. And I really don't like using software only Google knows how to support (=> Chromium). Sometimes I even think about migrating to SeaMonkey
But for example, you unfortunately can't properly debug multi threaded WASM code in Firefox.
https://bugzilla.mozilla.org/show_bug.cgi?id=1589908
Have a look at the Firefox developer tools' debug tab with this page opened. And it will list the threads (web workers) named with some randomized UUID. Impossible as a daily development driver :-/
https://zetaoffice.net/demo2.html
Chromium's Sources tab properly shows each thread's name. So I can easily spot "em-pthread_1" which contains the LibreOffice main thread.
But have a look at this line and you'll spot some extra code I added for running in Firefox :-)
https:/
Read the rest
/github.com/allotropia/zetajs/blob/8258649a7b98fd6af9...
If you have an idea for how to fix a Firefox specific problem, please file an issue and I promise to check if we can integrate the fix.
From the description here[1], it sounds like they're using WASM builds of LO.
I'm not quite interested enough to spend the CPU cycles it'd take to build and see whether that is really the whole story.
[1](https://github.com/allotropia/zetajs?tab=readme-ov-file)
In ZetaOffice: LibreOffice in the BrowserIt looks like they've developed a javascript library that interacts with a WASM build of LibreOffice:
https://github.com/allotropia/zetajs?tab=readme-ov-file
In ZetaOffice: LibreOffice in the BrowserIf you could file an issue please, at https://github.com/allotropia/zetajs/issues (with os version & hardware, if relevant)?
In Show HN: ZetaJS – client-side LibreOffice widget and automation in the browserShow HN: ZetaJS – client-side LibreOffice widget and automation in the browser
ZetaJS wraps ZetaOffice, a WASM version of LibreOffice - and makes accessing the entire gamut of the LibreOffice programmability interfaces from JavaScript convenient, idiomatic & extremely fast.
If you always wanted an entire client-side office suite in the browser, that you could fully automate with JS & seamlessly embed in your web apps - and on top of that, be able to self-host it & keep all data on the client, since there's literally no server involved (except for some static wasm & JS blobs) - then this might be for you.
5 points · Open discussion