product updates: march 1, 2026

a short ship: we fixed arena export in production, refreshed the README so it matches the product, and resolved the ESLint errors that were failing the build. nothing flashy — just the kind of fixes that keep parasol.so deployable and understandable.

---

arena export: no more read-only filesystem errors

on Vercel, the server runs on a read-only filesystem. the arena export flow used to POST data to /api/arena-export, which tried to write arena-data-export.json to disk. that triggered EROFS: read-only file system in production.

what we changed: the API no longer writes to the server. it returns the arena data as the response body with a Content-Disposition: attachment header. the client receives the response, creates a blob, and triggers a download in the browser. you click "Export Data" and get arena-data-export.json the same way — it just comes from the response instead of a file on the server. export now works on parasol.so.

---

README: current state of the project

the GitHub README was still describing an older layout (e.g. "main dashboard" as the root) and missing whole sections of the app. we rewrote it so it reflects what Parasol is today:

no new features; the README now matches the repo and the site.

---

build fixes: unescaped entities

the production build was failing on react/no-unescaped-entities: literal quote and apostrophe characters in JSX. we escaped them so the build passes:

after these changes, npm run build completes successfully. the app deploys to Vercel without lint errors blocking the build.

---

summary

all of this is on main and live at parasol.so. if you use Export Data on the Final Stretch arena, you get a clean download of your arena data in production as well as locally.