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 🙏

© 2025 – Pkg Stats / Ryan Hefner

docs-handler

v0.16.1

Published

This project is meant to render templates, compose documents and output generated content as is or pdf.

Downloads

11

Readme

Doc Generator

This project is meant to render templates, compose documents and output generated content as is or pdf.

Structure

  1. Template render
    • ejs implemented with async option enabled by default
  2. Template composition
    • the base structure expected makes possible to organize templates orderly and recursively

Templates

To make the best use of this you can find the base entities structure at /test/entities. They are not mandatory, but the template config structure is (you can only change field names)

Template Config sample

    {
        "config": {},
        "template": {
            "defaultConfig": {
                "outputType": "PDF"
            }
        },
        "templateContents": [
            {
                "name": "",
                "config": {
                    "order": 0,
                    "type": "HTML",
                    "ejsConfig": {}
                },
                "options": {
                    "subtitle": "test"
                },
                "content": "<h1>HTML <%=title%> - <%=options.subtitle%></h1>"
            },
            ...
        ]
    }

Rendering

To start rendering templates follow the example below

    // minimal and mandatory configuration below
    const builderConfig: DeepPartial<DomainOptions> = {
        templateConfig
    };
    const renderingData = {
        // data used into templates
    };

    const builder = new DocGeneratorBuilder();
    const { path } = await builder.generate(
        builderConfig,
        renderingData
    );

"builderConfig" can receive many customizations like: - file.dirPath: directory to store the file (or file.generate.dirPath specifically for rendering) - file.fileSystem: instance used to store content into a file - fileSystem is an instance of brunnofoggia/cloud-solutions storage, a lib that allows you to connect to different storages like aws.s3 gcp.storage or local.storage - file.name: template (lodash/template) of filename

  • any of these configurations can be set specifically for generate or output as shown below:
    {
        file: {
            generate: {
                dirPath,
                name,
                fileSystem
            },
            output: {
                dirPath,
                name,
                fileSystem
            }
        }
    }

Converting rendered content

  • For now only pdf convertion is available Looking at template config sample you see "outputType" set as "PDF" (it can be set into templateConfig.config or templateConfig.template.defaultConfig) Using the same configuration of previous example you can have a pdf as an output just changing the "generate" method for "generateAndOutput" as the code shown below:
    const { path } = await builder.generateAndOutput(
        builderConfig,
        renderingData
    );

Also if you need just to convert a html you already have, you can use pdf class directly. See the example below:

    import { PDFOptions } from 'puppeteer';
    import { PdfGenerator } from 'doc-generator/lib/outputs/pdf';

    const pdfConfig: DeepPartial<PDFOptions> = {}; // look into puppeteer docs
    const pdfGenerator = new PdfGenerator();
    const { path } = await pdfGenerator.generate({
        fileSystem,
        path,
        content,
        config: pdfConfig
    });