You need the dist/ folder. It contains a native binary and a bundled
Chromium — nothing else to install.
Mac: — double-click LookOut.app.
(To run with CLI flags right click LookOut.app > Show Package Contents > Contents/MacOS/LookOut)
Windows: — double-click LookOut.exe (or run.bat), or in a terminal:
LookOut.exe
Linux:
chmod +x run.sh # first time only
./run.shA Chrome window opens. Log in, browse the calendar months you want,
press Enter. events.ics is saved next to the binary.
Import into Google Calendar
- Open calendar.google.com
- Settings ⚙ → Import & Export → Import
- Choose
events.ics, pick your target calendar, click Import
node build.mjs builds a binary for the current platform only.
pkg cannot cross-compile on Windows (known upstream bug).
npm install
npx playwright install chromium # ~170 MB, one-time
node build.mjs # produces dist/To build for all platforms at once, use GitHub Actions — push the
repo and the included workflow (.github/workflows/build.yml) will
build on real Windows, Mac (ARM + Intel), and Linux runners and
attach the binaries to a release. Trigger it by pushing a version tag:
git tag v1.0.0 && git push origin v1.0.0Or trigger it manually from the Actions tab without a tag.
| Flag | Default | Description |
|---|---|---|
--out FILE |
events.ics | Output filename |
--folder-id ID |
(hardcoded) | Override the calendar folder filter |
--a |
false | Include Group A events and exclude Group B |
--b |
false | Include Group B events and exclude Group A |
--diagnose |
false | Dump raw event data and folder map, then exit |
"No events were converted" → Browse in Month view and page through the months you want before pressing Enter.
Wrong folder / missing events
→ Run node sync.js --diagnose, check diagnose_folders.json to find the
right folder ID, then pass it via --folder-id.
Timings are wrong after import
→ Ensure you're using the latest events.ics. The file embeds an
Australia/Sydney VTIMEZONE block that Google Calendar understands correctly.