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

daub

v1.3.0

Published

Templating engine with Whiskers-like syntax.

Downloads

16

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

antaranianantaranian

Keywords

Readme

Daub Build Status

A templating engine with Mustache-like syntax based on Whiskers.

Installation

Using component:

$ component install daub/daub

Using npm for server-side use or for browserify:

$ npm install daub

Example

Templates are rendered as follows, where "template" is a string and "context" is an object:

var daub = require('daub');

var template = 'Hello, {place}!',
    context  = { place: 'Region' };

daub.render(template, context); // Hello, Region!

A template might look something like this:

<article>
  {if tags}
    <ul id="tags">
      {for tag in tags}
      <li>{tag}</li>
      {/for}
    </ul>
  {else}
    <p>No tags!</p>
  {/if}
  <div>{content}</div>
  {!<p>this paragraph is 
    commented out</p>!}
</article>

With the following context:

{
  title: 'My life',
  author: 'Bars Thorman',
  tags: [
    'real',
    'vivid'
  ],
  content: 'I grew up into a fine willow.'
}

It would be rendered as this:

<article>
  <ul id="tags">
    <li>real</li>
    <li>vivid</li>
  </ul>
  <div>I grew up into a fine willow.</div>
</article>

Partials

Daub's partials are being loaded compile-time, like includes in EJS, so are not available for front-end usage.

You can specify partials using local files, using relative path to target template in statement. If specified path is a directory, it'll resolve corresponding index.html if exists.

<body>
  {>./common/header.html}
</body>

Or you can use npm or component packages, in which case template.html file or the one specified in manifest as template will be loaded.

<body>
  {>component/tip}
</body>

NOTE: By default npm is used to resolve packages. If you want to use component, set { component: true } in options argument.

Test

Run unit tests:

$ make test

Best practices

Use Whiskers.js instead, it's ~3x faster (could get even faster because of internal caching).

Forebears

License

The MIT License.