Savior

Hi HN, I built Savior, a tiny, dependency-free JavaScript library that autosaves form input and restores it after refreshes, tab closes, or browser crashes. It’s fully client-side, framework-agnostic, and designed to handle real-world edge cases like dynamic fields, corrupted storage, and failed submits without crashing the app. Savior restores drafts verbatim — no judgment, no “smart” recovery — just predictable behavior. GitHub: https://github.com/Pepp38/Savior Docs: https://zippers.dev Happy to answer questions.

I'm incredibly confused. The HN title is totally different from the article title, the article doesn't even contain the word "autosave" anywhere. Autosave is usually associated with something like Microsoft Word. As far as I can tell, this is about a JavaScript library for restoring HTML form values if something goes wrong. OK, sure that's a form of autosave. But then the HN title is "autosave is not recovery" which... huh? Isn't the article saying it is for recovery? Also, the article is a bunch of confusing philosophizing and doesn't really explain anything at all. The linked GitHub repo at the end is infinitely more informative: https://github.com/Pepp38/Savior

Savior is a tiny, dependency-free JavaScript library that prevents users from losing form input after refresh, navigation, tab close, or browser crashes. It handles real-world edge cases like corrupted storage, dynamic forms, and partial failures. No backend, no sync, no framework coupling. Tested with 18 automated suites and a 25-scenario manual crash-test matrix.