Files
Brandon ThomasandClaude Opus 5.5 ebc73bb7b4 Issue #107: Web build: data-safety fixes for libraries kept in the browser
- File > Back Up Library... (web): a zip of the catalog files and every
  stored original, built entry by entry; Restore Library from Backup...
  reads it into a new library folder and switches only when complete
  (the previous library stays in storage).
- Failed flushes to browser storage make the catalog Store refuse
  writes, so changes show as unsaved (top-bar warning) and are retried
  every 2 s instead of being lost silently.
- A picked/dropped photo whose bytes can't be stored is not added.
- One tab per library (Web Locks); a second tab shows a message.
- Notices: storage not persistent, library failed to open (temporary
  session), experimental build; ?reset asks first; a panic shows a
  message instead of a frozen page; long toasts wrap.
- Hosting: _headers/.htaccess no longer mark the unhashed .js/.wasm
  immutable; HOSTING.md rewritten for the actual build.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-05 17:46:21 -04:00

10 lines
373 B
Plaintext

# Netlify / Cloudflare Pages header rules (see HOSTING.md). Other hosts: set the same headers.
# The file names don't change between versions: revalidate them (no `immutable`), or an upgrade
# could leave browsers with an old module, or old glue next to a new module.
/*
X-Content-Type-Options: nosniff
Cache-Control: no-cache
/*.wasm
Content-Type: application/wasm