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

connect-lb-include

v0.3.0

Published

Connect middleware for `#include`-ing HTML files inside other HTML files, using `lb-include`

Downloads

6

Readme

connect-lb-include

Library for using lb-include as connect middleware (perhaps in an express app).

This will apply lb-include to all responses where Content-Type: text/html is set.

Builds hosted by Travis CI: master: , develop:

Install

$ npm install --save-dev connect-lb-include

Getting Started

For a fuller demo, look at demo/demo.js in this repo (and run it!). Here's an example of basic usage:

var express = require('express'),
    lbInclude = require('connect-lb-include'),
    serveStatic = require('serve-static');

var app = express();
app.use(lbInclude({ root: __dirname }));
app.use(serveStatic(__dirname));
app.listen(9000);

Anytime something with a Content-Type of text/html is returned by your routes, it will automatically get passed through lb-include by this middleware.

Configuration

You can pass an optional configuration object, which will be passed through to lb-include.

var app = express();
app.use(lbInclude({ ... }));
app.use(serveStatic(__dirname));
app.listen(9000);

You can pass any option supported by lb-include (see the documentation for lb-include for the entire list).

root directory

If you do not pass a root option, it will be assumed to be process.cwd()

The root option controls what the root directory is. This is passed as the root directory to lb-include, which uses it to resolve root-relative #include file paths (like <!-- #include file="/foo.html" -->).

When lb-include resolves relative include paths, it does so relative to the file. For connect-lb-include, the request URL is sanitized and mapped onto root, and that resulting location is used to resolve file-relative #includes (e.g. a response at URL /foo/bar/baz.html would be considered to be at <root>/foo/bar/baz.html for #include purposes.

License

Released under the MIT license © Jeffrey Stanton

See LICENSE.md for full license text