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

revise-static-content

v0.2.0

Published

Utility for updating static documentation in a repository.

Downloads

393

Readme

Revise Static Content

revise-static-content

Managing static documentation within your repository becomes effortless with this tool, which dynamically renders content into markdown files. Why?

Why?

Maintaining and synchronizing content across various files can be challenging, often leading to tedious copy-pasting tasks. Consequently, updating these files later becomes a nightmare, resulting in outdated documentation.

How it works

The package introduces "directive" comments capable of rendering content within specified tags. Since the comments themselves remain intact, the content can be dynamically re-rendered.

<!-- #directive: ... -->
some generated content
<!-- /directive -->

Usage

Simply provide a glob pattern to the CLI. It will then render all dynamic content within the directives and overwrite the files accordingly.

revise-static-content **/README.md

Directives

Include

This directive allows for the inclusion of content (parts) from other markdown files. The included content also supports template syntax.

<!-- @include: docs/parts/intro.md -->
This code is automatically generated and should be edited elsewhere.
<!-- /include -->

Insert

Inserts a template specified inline in the directive paramater.

<!-- @insert: Hello {{name}}! -->
Hello John!
<!-- /insert -->

Templates

Templates are snippets of code whose content can be overwritten. Templates can only be written in dynamic parts used by the include directive, or inline in the insert directive. Templates allow you to insert values defined in the frontmatter.

Hello {{name}}!

Ignoring

You can ignore rendering templates by wrapping the content in the ignore directive.

<!-- @ignore -->
This is how you write mustache `{{name}}`!
<!-- /ignore -->