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

less-express

v1.1.0

Published

express middleware for artifact free LESS compiling

Downloads

1,140

Readme

less-express

Build Status

express middleware for artifact free LESS compiling

Why another LESS middleware?

All existing LESS middlewares for express use a file based approach. This is great for big projects that require complex structures and high performance, yet this comes with two drawbacks: they generate build artifacts and complex setup. Sometimes you just want your app to serve a single CSS resource.

Installation

Install from npm:

$ npm install less-express --save

Usage

A simple example showing you how to serve the compiled version of ./public/stylesheets/app.less at /css/app.css:

var lessExpress = require('less-express');
app.get('/css/app.css', lessExpress('./public/stylesheets/app.less'));

Configuration

You can configure the middleware by passing options to LESS or the middleware itself:

app.get('/css/app.css', lessExpress('./public/stylesheets/app.less', lessOptions, middlewareOptions));

lessOptions will be passed through to LESS. See the LESS documentation for available configuration. The following middlewareOptions are available for the middleware:

  • cache: TTL in milliseconds that compilation results will be cached. When true is passed the cache will keep the initial compilation result infinitely. By default the middleware uses infinite caching in production. If you want to disable this pass false.
  • precompile: Tell the middleware to precompile the stylesheet on application startup. This is happening per default in production and can be disabled by passing false. If you explicitly set cache to false this will do nothing.
  • stale: If true then the middleware will return a stale cache of the stylesheet, if available, when a compilation error is encountered. This is false by default. If you explicitly set cache to false this will do nothing.
  • passThru: If true then the middleware will not send the response and instead will assign the resulting stylesheet to res.locals.lessCss using the given location and call the next middleware. i.e
lessExpress.options({passThru: true});
app.get('/css/app.css', lessExpress('./public/stylesheets/app.less'), function (req, res, next) {
    var css = res.locals.lessCss['./public/stylesheets/app.less'];
});

This is useful for extra processing you may want to apply after compilation, but before sending the response. This is false by default.

You can also set global configuration options that will be applied to all calls by using #lessOptions and #options:

lessExpress.options({cache: false});
lessExpress.lessOptions({plugins: [cleanCSS]});

Options passed to the function invocation will take precedence:

lessExpress.options({cache: false});
app.get('/css/app.css', lessExpress('./public/stylesheets/app.less', {}, {cache: 3600})); // will cache

License

MIT © Frederik Ring