pacexy flow: a Next.js epub reader with changesets installed, no changeset directory, and yarn in the Dockerfile
Browser-based ePub reader
At a glance
- What is it?
- A browser-based epub reader built on React, Next.js and Epub.js, self-hostable through a Dockerfile or compose file on port 3000. The last commit on main is dated 2026-03-28, the repository has no releases, the versioning tool is a dev dependency with no changeset directory in the tree, and the container build installs its task runner with yarn while everything else uses pnpm.
- Who is it for?
- This reader fits someone who wants to host their own epub reader rather than upload a library to someone else's server, and who is comfortable with a Next.js deployment and a compose file. Its feature list is short and specific, covering in-book search, annotations, typography, sharing by link, data export and cloud storage, and the roadmap behind those links is not in the repository.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Activity is slowing. The repository last received commits 7 months ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- pacexy/flow3,384 ★ · +46
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| pacexy/flow | 3.3k | 3.4k |
46 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The last commit is dated 2026-03-28 and there are no releases
Two facts about the state of the repository, both of them checkable in one glance at its metadata. The default branch is main and its most recent commit is dated 2026-03-28. And the repository has no GitHub releases at all, so there is no tag to pin, no changelog to read and no artifact to compare a deployment against. What the project does have is a version scheme in the manifest itself, where `packageManager` is pinned to a specific pnpm release with a full integrity hash appended to it, which is a level of pinning that usually comes with a release process in mind. None of that adds up to a published history here. The homepage is a separate site, flowoss.com, and the README describes the software as free, open source and browser-based, with the reader itself being the only thing in this repository.
Changesets is installed and the release script publishes, but the directory is absent
The root manifest carries `@changesets/cli` at 2.22.0 and `@changesets/changelog-github` at 0.4.4 in devDependencies, and a script named `release` whose body is `pnpm -r publish --access public`. So the intent to version and publish the workspace packages is declared twice over. Neither half has a counterpart in the repository. There is no `.changeset/` directory among the twenty-four top-level entries, which is where that tool records pending changes, and the repository has no releases, so nothing has ever come out of the pipeline in this tree. The root package is itself marked private, so `pnpm -r publish` is aimed at the workspace members rather than the root, which is the usual arrangement, and the workspace members are in `packages/` and `apps/`. The README names no shared package, so what would be published to a registry is not documented anywhere in it.
The Dockerfile installs turbo with yarn while the project is pnpm
Three package managers appear across the build, and only one of them is the project's. The prerequisites tell you to install pnpm, the development steps use `pnpm i` and `pnpm dev`, the manifest pins pnpm, and the installer stage of the image runs `corepack enable` followed by `pnpm i --frozen-lockfile`. The builder stage, one stage earlier, runs `yarn global add turbo` to get the task runner onto the PATH before `turbo prune` is used. So the image installs its build orchestrator with one package manager and the workspace it needs to build with another. The prune step scopes the build to a single application, `--scope=@flow/reader`, which matches the reader app the compose file and the manual run command both refer to by its directory name.
The container definition is an upstream template pinned to one commit
The first line of the Dockerfile is a comment holding the URL of Vercel's own turborepo example, pinned to a specific commit hash, and the rest follows that file's structure: a builder stage that installs libc6-compat, prunes the workspace and adds turbo globally, an installer stage that copies the pruned lockfile and package files, enables corepack and runs a frozen pnpm install before building with `DOCKER=1 pnpm -F reader build`, and a runner stage. That last stage creates a system group and user both with uid and gid 1001, switches to it, copies the standalone build output and the static assets with matching ownership, and runs `node apps/reader/server.js`. Worth noticing: the image declares no exposed port at all, while the compose file publishes 3000 and the README's manual run maps 3000 to 3000.
A Node 18 base with a 2023-vintage toolchain
All three image stages build on `node:18-alpine`, and the manifest requires Node 18 or newer. Around that sit pinned versions of the whole toolchain: TypeScript 4.6.3, ESLint 8.13.0 with `eslint-config-next` 12.1.5, Prettier 2.6.2 with its Tailwind plugin, Turbo 1.11.3, tsup 5.12.7 and Rollup 2.72.1. The ESLint configuration is the legacy format, a `.eslintrc.js` file, which is the shape ESLint 8 accepted before the flat config file became the default. Commit hooks are wired through husky with a `prepare` script that runs its install command, and `lint-staged` formats JavaScript, JSON, CSS, TypeScript, Markdown and MDX with Prettier, plus YAML except the pnpm lockfile, and applies `eslint --fix` to JavaScript and TypeScript. A `prettier.config.js` is committed at the root; there is no Prettier ignore file in the tree.
Self-hosting needs the environment file in place first, and the plan lives on Notion
The self-hosting section is careful about one thing and quiet about the rest. It points back at the environment setup step first, and both deployment routes depend on it: the compose file declares an `env_file` of `./apps/reader/.env.local`, so the file has to exist on the host before `docker compose up -d` will do anything, and the manual route passes the same path to `docker run`:
docker build -t flow .
docker run -p 3000:3000 --env-file apps/reader/.env.local flowThe compose file carries a `version` key set to 3.8, publishes 3000 to 3000, and restarts the container always. The reader itself offers nine features in a flat list, from grid layout and in-book search to highlights and annotations, themes, sharing a book by link, data export and cloud storage. Where it is going next is not in this repository: the roadmap link points at a Notion page, with the page identifier and a view parameter visible in the URL.
Editorial conclusion
This reader fits someone who wants to host their own epub reader rather than upload a library to someone else's server, and who is comfortable with a Next.js deployment and a compose file. Its feature list is short and specific, covering in-book search, annotations, typography, sharing by link, data export and cloud storage, and the roadmap behind those links is not in the repository. Before you build on it, weigh three things. The last commit on main is dated 2026-03-28 and the repository has no releases, so there is no version history to point at and nothing to upgrade to. The release machinery is installed without its configuration directory, so the packages are published by a script whose version record is not in the tree. And the container build is a copy of an upstream template that reaches for yarn in its first stage while the project is pnpm throughout, which is exactly the kind of detail worth reading before you trust an image.
Frequently asked questions
What is pacexy flow?
An AGPL-licensed, browser-based epub reader built with React, Next.js and Epub.js, credited also to TypeScript, Vercel and Turborepo. Its feature list covers grid layout, search within a book, image preview, custom typography, highlights and annotations, themes, sharing a book by link, data export and cloud storage, and it can be self-hosted.
How do I self-host the pacexy flow epub reader?
Set the environment variables first by copying the `.env.local.example` files to `.env.local`, because the compose file reads `./apps/reader/.env.local` through `env_file`. Then either run `docker compose up -d`, or build the image with `docker build -t flow .` and start it with `docker run -p 3000:3000 --env-file apps/reader/.env.local flow`.
How do I run pacexy flow from source while developing?
You need Node.js, pnpm and Git. Clone the repository, run `pnpm i`, copy every `.env.local.example` to `.env.local` and set the variables, then `pnpm dev`, which runs the Turbo pipeline in parallel across the workspace. The node requirement is 18 or newer.
Is there a pacexy flow Android app?
Nothing in the repository builds one. The deliverable is a browser-based web app with a container image, and the roadmap that might mention a mobile version is an external Notion page linked from the README rather than anything held here.
How is pacexy flow versioned and released?
Through changesets in principle: `@changesets/cli` is a dev dependency and the root has a `release` script running `pnpm -r publish --access public`. In practice the tree holds no `.changeset/` directory and the repository has no releases, and the last commit on main is dated 2026-03-28.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/pacexy-flow)Star history chart for your README
[](https://hysenlabs.com/projects/pacexy-flow)Was this useful?