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

precedent

v1.0.15

Published

Precedent Meta-Templating

Downloads

578

Readme

Precedent

Precedent meta-templating engine, for when you want templates ... for templates.

Code Climate Build Status Dependency Status devDependency Status

Template Patterns

Precedent works on the concept of "Template Patterns". These are regions of text that are replaced by their template function. Because patterns are defined in a tree data structure, nested patterns (such as <%, <%=, <$$ and <) properly get parsed in the same process run.

So, for instance, you could create a pattern like so:

// Load the precedent library
var libPrecedent = require('../source/Precedent.js').new();

// Add the pattern
libPrecedent.addPattern('{Name', '}', 'David Bowie');

// Parse a string with the pattern
console.log(libPrecedent.parseString('This is just a short message for {Name}.');
// Anything inbetween the start and end is ignored in this case, since it is a string substitution.
console.log(libPrecedent.parseString('This is just a short message for {Name THIS TEXT IS IGNORED}.  We hope to ignore the previous text.');

This would output the following to the console:

This is just a short message for David Bowie.
This is just a short message for David Bowie.  We hope to ignore the previous text.

precedent.addPattern(patternStart, patternEnd, parser)

Add a pattern to the string processor.

// Pass in a string
libPrecedent.addPattern('{Name', '}', 'David Bowie');

// Or a function
libPrecedent.addPattern('{Name', '}', (pString)=>{return pString.length;});

Each time a pattern is matched, anything between the patternStart and patternEnd will be passed into the parse function.

patternStart

Type: String

The beginning portion of a pattern.

patternEnd

Type: String

The ending portion of a pattern.

parser

Type: String or Function Default: Echo content between the pattern start and end.


precedent.parseString(contentString)

Parse a string with the processor.

libPrecedent.parseString('This is just a short message for {Name}.'

contentString

Type: String

The string of content to parseg