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

pdc-ts

v1.0.2

Published

Pandoc wrapper for Typescript applications running on NodeJS

Downloads

42

Readme

Pdc-ts

Pandoc wrapper for Typescript applications running on NodeJS

Installation

npm install pdc-ts

This package requires pandoc to be installed. By default, the wrapper assumes pandoc to be in PATH. To override this, see usage below.

Usage

import { PdcTs } from 'pdc-ts';

// Optional, if pandoc is not in PATH
const path = '/path/to/pandoc';
const pdcTs = new PdcTs(path);

// Now specify the details & execute
const result: string = await pdcTs.Execute({
    from: 'markdown', // pandoc source format
    to: 'html', // pandoc output format
    outputToFile: false, // Controls whether the output will be returned as a string or written to a file
    pandocArgs?: ['-v'], // pandoc arguments (any arguments you might want to pass to pandoc)
    spawnOpts?: {}, // NodeJS spawn options (leave empty if you don't know what this is)
    sourceText?: '# Heading', // Use this if your input is a string. If you set this, the file input will be ignored
    sourceFilePath?: '/some/path/to/some/file', // Use this is your input is a file. Only works if no string input was given
    sourceEncoding?: 'utf8', // Defaults to utf8
    destFilePath?: '/some/path/to/some/output' // This will be the output file destination if outputToFile is true
});

The result will either be a string containing the converted document or an empty string if you asked for a file as output. You can control this using the outputToFile boolean.

Credits

Thank you to John MacFarlane for creating Pandoc & Paul Vorbach for the original pdc wrapper I used as a basis for the Typescript version.

License

MIT