Skip to content


Repository files navigation

NodeJS / TypeScript Readium-2 "LCP" components

NodeJS implementation (written in TypeScript) of LCP modules for the Readium2 architecture ( ).


Build status

NPM David



  1. NodeJS >= 8, NPM >= 5 (check with command line node --version and npm --version)
  2. OPTIONAL: Yarn >= 1.0 (check with command line yarn --version)

GitHub repository

There is no site for this project (no gh-pages branch).

NPM package

Command line install:

npm install r2-lcp-js OR yarn add r2-lcp-js

...or manually add in your package.json:

  "dependencies": {
    "r2-lcp-js": "latest"

The JavaScript code distributed in the NPM package is usable as-is (no transpilation required), as it is automatically-generated from the TypeScript source.

Several ECMAScript flavours are provided out-of-the-box: ES5, ES6-2015, ES7-2016, ES8-2017:

(alternatively, GitHub mirror with semantic-versioning release tags: )

The JavaScript code is not bundled, and it uses require() statement for imports (NodeJS style).

More information about NodeJS compatibility:

Note that web-browser Javascript is currently not supported (only NodeJS runtimes).

The type definitions (aka "typings") are included as *.d.ts files in ./node_modules/r2-lcp-js/dist/**, so this package can be used directly in a TypeScript project.

Example usage:

// currently no index file
// import { * } from "r2-lcp-js";

// ES5 import (assuming node_modules/r2-lcp-js/):
import { downloadEPUBFromLCPL } from "r2-lcp-js/dist/es5/src/publication-download";

// ... or alternatively using a convenient path alias in the TypeScript config (+ WebPack etc.):
import { downloadEPUBFromLCPL } from "@r2-lcp-js/publication-download";


A package-lock.json is provided (modern NPM replacement for npm-shrinkwrap.json).

A yarn.lock file is currently not provided at the root of the source tree.

Continuous Integration

TODO (unit tests?)

Badge: [![Travis](](

Version(s), Git revision(s)

NPM package (latest published):

Alternatively, GitHub mirror with semantic-versioning release tags:

Developer quick start

Command line steps (NPM, but similar with YARN):

  1. cd r2-lcp-js
  2. git status (please ensure there are no local changes, especially in package-lock.json and the dependency versions in package.json)
  3. rm -rf node_modules (to start from a clean slate)
  4. npm install, or alternatively npm ci (both commands initialize the node_modules tree of package dependencies, based on the strict package-lock.json definition)
  5. npm run build:all (invoke the main build script: clean, lint, compile)
  6. ls dist (that's the build output which gets published as NPM package)