Is this project abandoned?

[ankified]

The website is not working and the last commit was about 3y ago.
Is it still usable?

[AntonOfTheWoods]

The website is not working and the last commit was about 3y ago.

That looks like the very definition of "abandoned"! You could always fork if there are bugs that annoy you...

[tishihtzu]

There has not been a release in two years and there are 32 pull requests-- that does not sound actively maintained to me...

[bernie43]

I searched around for a bit, and this seems to be the only proper alternative now:
https://github.com/johnfactotum/foliate-js

[HadrienGardeur]

I'm the project manager for Readium Mobile/Web and Thorium Mobile/Web.

We've been working on an open-source toolkit for the Web for a few years now (what we call Readium Web is based on the TypeScript Toolkit and the Go Toolkit) and we've also been building a product for a year now built on top of the TypeScript toolkit (Thorium Web).

Readium Web has been used in production for over 3 years now, while Thorium Web is being progressively adopted by various organizations, including the Internet Archive, New York University Press and multiple content aggregators.

Thorium Web supports EPUB (both reflowable and fixed layout) and can be tested at https://playground.readium.org

We plan on adding support for audiobooks, comics and PDF as well in the future, with a focus on audio right now (read aloud using text to speech, media overlays in EPUB and audiobooks).

All of these projects are available under a BSD-3 license and actively maintained (we have two maintainers on the toolkits and one on Thorium Web).

Thorium Web is quite different from EPUB.js though because it doesn't interact directly with EPUB files, instead it relies on a Readium Web Publication Manifest, which can be use with any publication format.

The typical deployment usually involves a server running the Readium CLI with the serve command alongside a deployment or a fork of Thorium Web.

[AntonOfTheWoods]

We've been working on an open-source toolkit for the Web for a few years now (what we call Readium Web is based on the TypeScript Toolkit and the Go Toolkit) and we've also been building a product for a year now built on top of the TypeScript toolkit (Thorium Web).

What is the relationship to d-i-t-a/reader? I had some pretty specific requirements a few years back and ended up having to vendor that and hack away to get something that sort of worked.

I basically need something that will recalculate the page size/length (and get it correct!) automatically very efficiently. I have to do it on a timer at the moment and it's HORRIBLE doing that. My pages are long with up to hundreds of thousands of Infernojs objects and regularly update, so recalculations can hide parts of the book if I'm not careful.

I've been looking to migrate back from readium to EPUB (even though I'm already parsing and rewriting the book on the server) in the hope of finding something less nasty...

[HadrienGardeur]

What is the relationship to d-i-t-a/reader?

No direct relationship.

d-i-t-a/reader uses some components from the Readium architecture (including the manifest and Readium CSS) but it's not an official Readium project.

Readium Web follows closely what has been done in Readium Mobile, unlike d-i-t-a/reader.

[Efreak]

Try https://github.com/intity/epub-js

[williamchong]

We are also trying to port epub.js to native typescript with minimal breaking changes for our own project 3ook.com
see if it fits your need
https://github.com/likecoin/epub.ts/