ZenNotes/zennotes v2.20.1

ZenNotes v2.20.1

on GitHub

ZenNotes 2.20.1: 2.20.0 could not start, this fixes it

If you updated to 2.20.0 and the app opened an error box instead of your notes, this is the release you want. Installers for macOS, Windows, and Linux (x64 + arm64) are attached below.

🐛 Fixes

• 2.20.0 would not launch. Every platform, every install, straight to "A JavaScript error occurred in the main process" with Cannot find package 'micromark-util-encode' and no window behind it. Nothing was wrong with your vault or your install, and downgrading to 2.19.0 was the right call while this was out.

  What happened: 2.20.0's new Word export made the main process the first part of the app to parse markdown, and it loaded its markdown parser from the packaged app's own node_modules on the way to opening a window. Those files are laid out by the packaging step, and it put one of them somewhere the loader could not follow: a package sitting at the top level needed a dependency that only existed nested inside another package, which is exactly the direction the resolver does not look. The very first import failed and the app stopped before it drew anything.

  The main process now carries its markdown parser inside its own bundle rather than looking it up at startup, so there is no longer a file layout for the packaging step to get wrong. That is a deliberately broader fix than pinning the one package that went missing, which would have left the next one free to fall through the same gap.

  On why it reached you: the app was driven and checked at length before release, but always as a build run from the source tree, where those files sit where the loader expects and everything starts normally. This failure only exists inside a packaged app, so the one check that would have caught it, installing the thing that actually ships and watching it open a window, is the check that was missing. It is being added.

There are no other changes since 2.20.0. Everything in the 2.20.0 notes, Workflows, custom code languages, folder remapping, the new exports, is in this release and unchanged.

Sorry for the bad update, and thank you to the person who reported it with the error text attached, which is what made it a ten-minute diagnosis instead of a hunt.

Keyboard-first and local-first, as always.