NodeJS / TypeScript Readium-2 "opds" components
NodeJS implementation (written in TypeScript) of OPDS functionality for the Readium2 architecture ( https://github.com/readium/architecture/ ).
Build status
Changelog
Prerequisites
- https://nodejs.org NodeJS >= 8, NPM >= 5 (check with command line
node --version
and npm --version
) - OPTIONAL: https://yarnpkg.com Yarn >= 1.0 (check with command line
yarn --version
)
GitHub repository
https://github.com/readium/r2-opds-js
There is no github.io site for this project (no gh-pages branch).
NPM package
https://www.npmjs.com/package/r2-opds-js
Command line install:
npm install r2-opds-js
OR
yarn add r2-opds-js
...or manually add in your package.json
:
"dependencies": {
"r2-opds-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:
https://unpkg.com/r2-opds-js/dist/
(alternatively, GitHub mirror with semantic-versioning release tags: https://github.com/edrlab/r2-opds-js-dist/tree/develop/dist/ )
The JavaScript code is not bundled, and it uses require()
statement for imports (NodeJS style).
More information about NodeJS compatibility:
http://node.green
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-opds-js/dist/**
, so this package can be used directly in a TypeScript project.
Dependencies
https://david-dm.org/readium/r2-opds-js
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?)
https://travis-ci.org/readium/r2-opds-js
Badge: [![Travis](https://travis-ci.org/readium/r2-opds-js.svg?branch=develop)](https://travis-ci.org/readium/r2-opds-js)
Version(s), Git revision(s)
NPM package (latest published):
https://unpkg.com/r2-opds-js/dist/gitrev.json
Alternatively, GitHub mirror with semantic-versioning release tags:
https://raw.githack.com/edrlab/r2-opds-js-dist/develop/dist/gitrev.json
Developer quick start
Command line steps (NPM, but similar with YARN):
cd r2-opds-js
git status
(please ensure there are no local changes, especially in package-lock.json
and the dependency versions in package.json
)rm -rf node_modules
(to start from a clean slate)npm install
, or alternatively npm ci
(both commands initialize the node_modules
tree of package dependencies, based on the strict package-lock.json
definition)npm run build:all
(invoke the main build script: clean, lint, compile)ls dist
(that's the build output which gets published as NPM package)
Documentation
(de)serialization / (un)marshalling of JSON and XML
Due to the "factory" registration pattern in the TA-JSON library dependency (and its corresponding XML fork/adaptation),
the functions initGlobalConverters_GENERIC()
and initGlobalConverters_OPDS()
must be called before invoking the actual OPDS1/2 parsers.
https://github.com/readium/r2-opds-js/blob/develop/src/opds/init-globals.ts
import { initGlobalConverters_GENERIC, initGlobalConverters_OPDS } from "@opds/init-globals";
initGlobalConverters_GENERIC();
initGlobalConverters_OPDS();
OPDS 1
The XML (Atom) markup of an OPDS1 "feed" (or "entry") can be loaded/parsed into an in-memory data model.
https://github.com/readium/r2-opds-js/tree/develop/src/opds/opds1
import * as xmldom from "xmldom";
import { XML } from "@utils/xml-js-mapper";
import { OPDS } from "@opds/opds1/opds";
import { Entry } from "@opds/opds1/opds-entry";
const xmlDom = new xmldom.DOMParser().parseFromString(xmlStr);
if (!xmlDom || !xmlDom.documentElement) {
return;
}
const isEntry = xmlDom.documentElement.localName === "entry";
if (isEntry) {
let opds1Entry = XML.deserialize<Entry>(xmlDom, Entry);
} else {
let opds1Feed = XML.deserialize<OPDS>(xmlDom, OPDS);
}
OPDS 2
The JSON serialization of an OPDS2 "feed" (or "publication") can be loaded/parsed into an in-memory data model.
https://github.com/readium/r2-opds-js/tree/develop/src/opds/opds2
import { TaJsonDeserialize, TaJsonSerialize } from "@r2-lcp-js/serializable";
import { OPDSFeed } from "@opds/opds2/opds2";
import { OPDSPublication } from "@opds/opds2/opds2-publication";
var opds2Feed: OPDSFeed;
const opds2Feed_JSON = TaJsonSerialize(opds2Feed);
opds2Feed = TaJsonDeserialize<OPDSFeed>(opds2Feed_JSON, OPDSFeed);
var opds2Publication: OPDSPublication;
const opds2Publication_JSON = TaJsonSerialize(opds2Publication);
opds2Publication = TaJsonDeserialize<OPDSPublication>(opds2Publication_JSON, OPDSPublication);
OPDS 1 - OPDS 2 Converter
An OPDS1 "feed" (or "entry") can be converted into an OPDS2 representation.
https://github.com/readium/r2-opds-js/blob/develop/src/opds/converter.ts
import * as xmldom from "xmldom";
import { XML } from "@utils/xml-js-mapper";
import { OPDS } from "@opds/opds1/opds";
import { Entry } from "@opds/opds1/opds-entry";
import { OPDSFeed } from "@opds/opds2/opds2";
import { OPDSPublication } from "@opds/opds2/opds2-publication";
import { convertOpds1ToOpds2, convertOpds1ToOpds2_EntryToPublication } from "@opds/converter";
const xmlDom = new xmldom.DOMParser().parseFromString(xmlStr);
if (!xmlDom || !xmlDom.documentElement) {
return;
}
const isEntry = xmlDom.documentElement.localName === "entry";
if (isEntry) {
let opds1Entry = XML.deserialize<Entry>(xmlDom, Entry);
let opds2Publication: OPDSPublication = convertOpds1ToOpds2_EntryToPublication(opds1Entry);
} else {
let opds1Feed = XML.deserialize<OPDS>(xmlDom, OPDS);
var opds2Feed: OPDSFeed = convertOpds1ToOpds2(opds1Feed);
}