MAmac-attack·Dec 28, 2025
I've used recalendar.js the past few years for my eInk devices:
https://github.com/klimeryk/recalendar.js
In Calendarklimeryk
recalendar.js
JavaScript2022–2025
klimeryk / recalendar.js
recalendar.js
ReCalendar - create your personalized calendar PDF for ReMarkable tablets
2Distinct people
4Mentions
0Explicit recommenders
425GitHub stars
What to know before exploring
What it is
ReCalendar - create your personalized calendar PDF for ReMarkable tablets
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 year4 dated mentions
Observed mentions: 2022-01-10 17:05:53 UTC to 2025-12-28 05:36:33 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 |
|---|---|---|---|---|---|
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 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 | 3 | 0 | 3 |
What Hacker News says
4 sourcesNice, TIL! I knew ReMarkable stored the written notes in a special file, but it sounded a bit hacky, so I did not want to touch that. Good to see someone managed to make it work! I'll have to look into it, thanks!
Edit: tracking here: https://github.com/klimeryk/recalendar.js/issues/23#issuecom...
In Sketchy CalendarReCalendar supports loading any ICS file - but since you ultimately generate a PDF for the whole year, it will just load the events present at that moment in the calendar (see https://github.com/klimeryk/recalendar.js/issues/11#issuecom...). So it's good for quickly loading all the holidays in a given country or if you have some long-term recurring events. But it's not feasible to keep on syncing the calendar every day.
In Sketchy CalendarHi, author here! I'm excited to share a project I created to scratch my itch: a generator of a PDF calendar for ReMarkable tablets (and possibly other e-ink devices). It's pretty niche, but I'm really happy how it turned out.
It started as a PHP script [1] to quickly verify the idea. I got lots of great feedback on it [2], plus I used it for a few months myself. But I've hit a few technical walls with the (otherwise very competent) PDF framework I chose [3]. Most notably, it only supported a subset of CSS and layout was done using tables (hello, 2000s!). This led to a growing list of pain-points (links did not span the whole cell, not easy to re-order elements, etc.). I also kept thinking on how to make this project more approachable - without needing to install and know a bit of PHP. However, since it was a PHP script, that meant PDF gen
Read the rest
eration on the backend. Which meant abuse protection, beefy server, etc.
So I rewrote the project from scratch [4], this time in JavaScript. Using react-pdf, I was able to move PDF generation entirely to client-side. It internally uses Yoga Layout, which means flexbox, finally! (subset, but still) React allowed me to extract and re-use components better. Internationalization was smooth as well. Web workers ensure the browser does not lock up (unless you're generating the full PDF in Firefox, for some reason...). Everything runs in client-side, no data is transferred to any servers. Privacy FTW!
There's many features available [5], but one I wanted to highlight here is how I've achieved sharing and preserving configuration (so that you can share it with friends or regenerate the calendar next year). Since I wanted to avoid storing any information on my or (even worse) third-party servers, the options were limited. Stuffing the data into the URL was probably possible. But it's unclear what are the safe limits of URL length. Plus, you can easily lose the URL. Downloading the data (a JSON file? Copy & paste?) was also clunky - how to explain to users what this file is? It can also be easily misplaced.
Then I realized - PDF files can have embedded file attachments :) So I'm saving the configuration file inside the generated PDF calendar. So if you ever want to reload the same settings (they are backwards compatible), you just upload the same PDF file (of course, PDF parsing happens on the client-side only as well). It's much safer approach and more intuitive - you will always have your PDF calendar file :)
In case you give my server the hug of death, the app is also available on GitHub Pages: https://recalendar.klimer.eu/
While the current version is tested only on ReMarkable tablets, it should be fairly easy to add support for other devices. Please open a new issue on GitHub, ideally with the specification of the device (screen size in pixels or mm).
[1] https://github.com/klimeryk/recalendar/
[2] https://www.reddit.com/r/RemarkableTablet/comments/odpl07/re...
[3] https://mpdf.github.io/
[4] https://github.com/klimeryk/recalendar.js/
[5] https://recalendar.me/features