epub-press-clients is the open-source client codebase for EpubPress, a service that stitches articles, blogs and webpages into a customized ebook, and it targets JavaScript developers, publishers and browser users who want ad-free reading on a Kindle, Nook, iPhone or Android device.

What it is

epub-press-clients is a JavaScript, GPL-3.0 repository that holds the client packages for EpubPress. It contains three of them: epub-press-chrome, the source code behind the Chrome extension that builds an ebook from articles in your currently open tabs; epub-press-js, a JavaScript library published to npm for creating books with EpubPress; and epub-press-widgets, a set of ready-to-use widgets for publishers, which the README lists under the roadmap rather than as a released package. The backend code lives in a separate repository, haroldtreen/epub-press, and the project homepage is https://epub.press.

The concrete problem it solves is the state of reading long-form material in a browser. Webpages carry boilerplate, navigation and advertising around the text, and collecting several articles into one readable file by hand is tedious. EpubPress takes a group of pages, extracts the article content, and produces a single EPUB that carries that content offline. The README states plainly that books remove website boilerplate and ads, and that the result is clean content. Content extraction relies on node-readability, and EPUB construction relies on nodepub.

Key capabilities

• Builds an ebook directly from the articles in your currently open browser tabs, using the epub-press-chrome extension distributed on the Chrome Web Store under id pnhdnpnnffpijjbnhnipkehhibchdeok.
• Ships epub-press-js on npm as a JavaScript library for creating books with EpubPress, so the same book-building flow can be driven from code.
• Strips site chrome, navigation and ads from source pages through node-readability, leaving the article text alone.
• Packages the result as EPUB with nodepub, producing files the README says work across iPhone, Android, Kindle and Nook readers.
• Groups collected articles into themed books, illustrated in the README by examples such as "News from this week" and "Top 10 travel articles".
• Offers epub-press-widgets so publishers can let their own users download site content as an ebook, with development and release still on the roadmap.
• Carries a published roadmap covering custom cover pages, extra metadata such as author, sharing of generated creations, and detection of pages that hold lists of links such as OneTab, Feedly and RSS feeds.

Who uses it and how

• Everyday browser readers who open several articles in tabs and want one offline EPUB for a Kindle, Nook, iPhone or Android reader instead of reading each page online.
• JavaScript developers who pull epub-press-js from npm and call it from their own tooling to generate books programmatically.
• Publishers who intend to embed epub-press-widgets so visitors can download site content in ebook form, though that package is not yet released.
• Self-hosters who run the companion backend from haroldtreen/epub-press, since this repository delivers clients only.

Getting started

Install the library with the npm package epub-press-js, or add the browser extension from the Chrome Web Store listing for EpubPress. The backend is not part of this repository and must be obtained separately from haroldtreen/epub-press.

How it compares

The facts provide no list of paid products that EpubPress replaces, and the README names no rival client application. The only adjacent tools it names are the libraries it depends on, node-readability and nodepub, plus the backend repository it pairs with, so on the evidence available this project stands alone in this registry.

When to use it — and when not to

This repository is clients only: anyone wanting the full EpubPress service must also deploy and run the separate backend, and the README gives no operational detail on what that deployment involves. The widget package is still on the roadmap rather than available, and the repository carries 96 open issues, so teams needing a finished publisher integration or predictable support should weigh that. Bug reports and help requests go through GitHub issues or support@epub.press, which is fine for a GPL-3.0 community project but not the same as commercial support.