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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@oziabr/pug-layers

v1.0.0

Published

Express middleware that extends res.render to serve pug templates at any layer of their extends chain

Downloads

18

Readme

pug-layers

Express middleware that extends res.render to serve pug templates at any layer of their extends chain — returning a fragment without outer wrappers.

Install

npm install pug-layers

Usage

const express   = require('express');
const pugLayers = require('pug-layers');

const app = express();
app.set('views', './views');
app.set('view engine', 'pug');

app.use(pugLayers);

// full page — normal Express behaviour, all layers rendered
app.get('/', (req, res) => res.render('page', locals));

// layer 0 — innermost block only, no nav, no layout
app.get('/fragment', (req, res) => res.render('page:0', locals));

// layer 1 — page content only, no nav
app.get('/partial',  (req, res) => res.render('page:1', locals));

// layer 2 — nav + page content, no layout shell
app.get('/with-nav', (req, res) => res.render('page:2', locals));

How layers map to your template chain

Given a three-level inheritance chain:

layout.pug          ← outermost — full HTML shell
  └─ nav.pug        ← layer 2 — nav + content
       └─ page.pug  ← layer 1 — page content
            └─ ...  ← layer 0 — innermost block only

Layer 0 is always the innermost block — the raw fragment with no wrappers. Each increment adds one outer layer. No layer suffix renders the full page as normal.

How it works

res.render('page:N', locals) compiles page.pug with a preCodeGen plugin that intercepts the fully-linked AST — after the entire extends chain has been resolved — and hoists the NamedBlock at depth N to the root, stripping all outer layers. Compiled functions are stored in pug.cache under filename:layer keys and reused on subsequent requests.

Debug

Uses the debug package under the express:pug-layers namespace:

DEBUG=express:pug-layers node app.js
DEBUG=express:*          node app.js

Template structure

Each level must declare a single named block as its contribution:

//- layout.pug
block main

//- nav.pug
extends layout
block main
  nav ...
  main
    block main_content

//- page.pug
extends nav
block main_content
  .page
    block body_content