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

budo-less

v1.0.1

Published

experimental dev server with LESS support

Downloads

20

Readme

budo-less

experimental

Experiments with LESS and budo. For a custom dev script, e.g. using PostCSS or SASS, see API Example.

Install

npm install budo-less -g

For pretty printing, you can pipe to garnish.

Example

budo-less src/index.js:bundle.js --live --less style.less | garnish

Now, when you hit http://localhost:9966/, the default HTML index will look like this:

<!doctype html>
<head>
  <title>hello</title>
  <meta charset="utf-8">
  <link rel="stylesheet" href="style.css">
</head>
<body>
  <script src="bundle.js"></script>
</body>
</html>

When the server requests style.css, it will pre-process your specified --less file on the fly, writing CSS to the response.

When you make changes to .less files in your working directory, it will trigger a CSS LiveReload without refreshing the page.

Usage

The CLI behaves like budo, with the following extra options:

Usage:
  budo-less [opts] -- [browserifyOpts]

Options:
  --live        enable LiveReload for HTML/LESS
  --less        path to your LESS entry point
  --css         optional URL for the CSS href
  --paths       optional list of paths for LESS (colon-delimited in unix)
  --autoprefix  optional; enable autoprefix for given browsers

The --css flag defaults to the filename of --less.

Examples:

budo-less foo.js --less=foo/main.less | garnish
budo-less foo.js --css=static/main.css --less=src/main.less
budo-less foo.js --less=main.css --autoprefix="last 2 browsers"

API Example

This is fairly simple to achieve using the budo API.

See test/api-example.js for an example of this.

License

MIT, see LICENSE.md for details.