npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@liprikon/epub-parser

v2.1.10

Published

A (fork of) powerful yet easy-to-use epub parser

Downloads

182

Readme

📖 epub-parser (fork)

A (fork of) powerful yet easy-to-use epub parser

npm version Test

The package exports a simple parser function which use epub file as input and output JavaScript object.

As it is written in TypeScript, types are already included in the package.

Install

npm install @gxl/epub-parser --save

or if you prefer yarn

yarn add @gxl/epub-parser

Usage

import { parseEpub } from '@gxl/epub-parser'

const epubObj = parseEpub('/path/to/file.epub', {
  type: 'path',
})

console.log('epub content:', epubObj)

parseEpub(target: string | buffer, options?: object): EpubObject

target

type: string or buffer

It can be the path to the file or file's binary string or buffer

options

type: object

type(optional): 'binaryString' | 'path' | 'buffer'

It forces the parser to treat supplied target as the defined type, if not defined the parser itself will decide how to treat the file (useful when you are not sure if the path is valid).

EpubObject

The output is an object which contains structure, sections, info(private property names start with _. I don't recommend using them, since they are subscribed to change).

structure is the parsed toc of epub file, they contain information about how the book is constructed.

sections is an array of chapters or sections under chapters, they are referred in structure. Each section object contains the raw html string and a few handy methods.

  • Section.prototype.toMarkdown: convert to markdown object.
  • Section.prototype.toHtmlObjects: convert to html object. And a note about src and href, the src and href in raw html stay untouched, but the toHtmlObjects method resolves src to base64 string, and alters href so that they make sense in the parsed epub. And the parsed href is something like #{sectionId},{hash}.

How to contribute

  • Raise an issue in the issue section.
  • PRs are the best.

❤️