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

@informatiqal/publiqate-html

v1.0.0

Published

Publiqate plugin to generate HTML files

Downloads

72

Readme

Publiqate HTML

Generate HTML file plugin for Publiqate

Build and Installation

Clone this repository. Navigate to the plugins -> html folder and run:

npm run build

Once the build process is complete the compiled code will be available in plugins -> html -> dist folder.

Copy the content of the dist folder somewhere on the server, where Publiqate is running and specify the location from where Publiqate will load the plugin.

Once the config is set either restart the Publiqate service or visit the admin UI and press "Refresh config".

Example config:

...
plugins:
  - c:\path\to\html\plugin\dist\index.js
...
notifications:
  - type: Stream
    ...
    callbacks:
      - type: html
        details:
          template: c:\path\to\template.handlebars # see Templates section for details
          path: c:\path\to\where\to\store\index.html
          type: handlebars # or ejs, pug, mustache
...

Options

  • template - full path to the template to use (see Templates section for details)
  • path- full path to where to store the compiled plugin. The path must include the file name as well
  • type - optional. defaults to handlebars. Which template engine to use to render the template (see the section below)

Templates

The plugin support 4 template engines:

For each template engine error log entry will be generated if the template fails to compile/render.

Examples how to render list of names for all entities in the notification for each template engine:

EJS

<ul><% entities.forEach((entity,index) => {%>
  <li><%= entity.details.name %></li><% }) %>
</ul>

Handlebars

<ul>
  {{#each entities}}
    <li>{{this.details.name}}</li>
  {{/each}}
</ul>

Pug

ul
  each n in entities
    li= n.details.name

Mustache

<ul>
  {{#entities}}
    <li>{{details.name}}</li>
  {{/entities}}
</ul>