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

markdown-engine

v0.0.2

Published

A markdown + {{}} engine for Express

Downloads

5

Readme

{{markdown}}

A lightweight markdown engine for Express.

Example

app.js

'use strict';

var express = require('express');
var markdownEngine = require('./util/markdown-engine');

var app = express();

app.engine('md', markdownEngine.configure());

app.set('views', path.join(__dirname, 'views'));
app.set('view engine', 'md');

...

views/layout.html

<!DOCTYPE html>
<html>
  <head>
    <title>{{title}}</title>
  </head>
  <body>
    {{body}}
  </body>
</html>

Templating

Templates are written using Markdown and provide basic templating features.

My middle name is {{name}}
res.render('template', { name: 'danger' });
My middle name is danger

Partials

Partials can be included by using the following syntax:

{{> partial}}
{{> path/to/partial}}

By default, partials are expected to be located in the views/partials/ directory.

Caching

Template caching is enabled only in production. NODE_ENV=production

API

configure: Function

The configure call accepts an Object as an argument. It is not required, but allows you to specify a basePath for the engine. By default partials and templates are expected to live in the views directory in the root of your project. If your this directory happens to be placed somewhere else, use basePath to define it.

app.engine('md', markdownEngine.configure({basePath: __dirname});