Paged.js - Paged Media Tools
NPM Module
$ npm install pagedjs
import { Previewer } from 'pagedjs';
let paged = new Previewer();
let flow = paged.preview(DOMContent, ["path/to/css/file.css"], document.body).then((flow) => {
console.log("Rendered", flow.total, "pages.");
})
Polyfill
Add the the paged.polyfill.js
script to replace all @page
css and render the html page with the Paged Media styles applied:
<script src="https://unpkg.com/pagedjs/dist/paged.polyfill.js"></script>
Try the polyfill with Aurorae.
By default the polyfill will run automatically as soon as the DOM is ready.
However, you can add an async before
function or return a Promise to delay the polyfill starting.
<script>
window.PagedConfig = {
before: () => {
return new Promise(resolve, reject) {
setTimeout(() => { resolve() }, 1000);
}
},
after: (flow) => { console.log("after", flow) },
};
</script>
Otherwise you can disable auto
running the previewer and call window.PagedPolyfill.preview();
whenever you want to start.
<script>
window.PagedConfig = {
auto: false
after: (flow) => { console.log("after", flow) },
};
setTimeout(() => {
window.PagedPolyfill.preview();
}, 1000);
</script>
Chunker
Chunks up a document into paged media flows and applies print classes.
Examples:
Polisher
Converts @page
css to classes, and applies counters and content.
Examples:
CLI
Command line interface to render out PDFs of HTML files using Puppeteer: https://gitlab.pagedmedia.org/polyfills/pagedjs-cli.
Modules
Modules are groups of handlers for that apply the layout and styles of a CSS module, such as Generated Content.
New handlers can be registered from import { registerHandlers } from 'pagedjs'
or by calling Paged.registerHandlers
on an html page.
<script src="https://unpkg.com/pagedjs/dist/paged.polyfill.js"></script>
<script>
class MyHandler extends Paged.Handler {
constructor(chunker, polisher, caller) {
super(chunker, polisher, caller);
}
afterPageLayout(pageFragment, page) {
console.log(pageFragment);
}
}
Paged.registerHandlers(MyHandler);
</script>
Handlers have methods that correspond to the hooks for the parsing, layout and rendering of the Chunker and Polisher. Returning an promise or async
function from a method in a handler will complete that task before continuing with the other registered methods for that hook.
beforeParsed(content)
afterParsed(parsed)
beforePageLayout(page)
afterPageLayout(pageElement, page, breakToken)
afterRendered(pages)
beforeTreeParse(text, sheet)
onUrl(urlNode)
onAtPage(atPageNode)
onRule(ruleNode)
onDeclaration(declarationNode, ruleNode)
onContent(contentNode, declarationNode, ruleNode)
Setup
Install dependencies
$ npm install
Development
Run the local dev-server with livereload and autocompile on http://localhost:9090/
$ npm start
Deployment
Build the dist
output
$ npm run prepare
Testing
Testing for Paged.js uses Jest but is split into Tests and Specs.
Tests
Unit tests for Chunker and Polisher methods are run in node using JSDOM.
npm run tests
Specs
Specs run a html file in Chrome (using puppeteer) to test against CSS specifications.
They can also output a pdf and compare pages (one at a time) in that PDF with samples PDFs (saved as images).
To test the pdf output of specs, you'll need to install ghostscript locally.
brew install ghostscript
npm install ghostscript4js --no-save
Then run the jest tests in puppeteer.
npm run specs
To debug the results of a test in a browser you can add NODE_ENV=debug
NODE_ENV=debug npm run specs
To update the stored pdf images you can run
npm run specs -- --updateSnapshot
Docker
A pagedmedia/pagedjs
docker image contains all the dependencies needed to run the pagedjs
development server, as well as the pdf comparison tests.
To build the image run
docker build -t pagedmedia/pagedjs .
By default the container will run the development server with npm start
docker run -it -p 9090:9090 pagedmedia/pagedjs
The tests and specs can be run within the container by passing a seccomp
file for Chrome and running npm test
docker run -it --security-opt 'seccomp=seccomp.json' pagedmedia/pagedjs npm test