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

buddy-server

v3.1.1

Published

A simple asset server and livereload server for Buddy projects.

Downloads

7

Readme

NPM Version

buddy-server

A simple development fileserver, with LiveReload support, for the buddy build tool.

WARNING: default fileserving is very permissive! This is inherently insecure, and therefore only recommended for local development.

When working with the LiveReload feature, it is recommended to install the LiveReload Chrome extension, or include the following in your html source to initiate the connection:

<script src="http://localhost:35729/livereload.js"></script>

Usage

{
  "devDependencies": {
    "buddy": "6.13.0",
    "buddy-server": "3.0.0"
  },
  "buddy": {
    "server": {
      "port": 8000,
      "directory": "www"
    }
  }
$ buddy watch --serve --reload

Specify multiple directories:

"buddy": {
  "server": {
    "port": 8000,
    "directory": ["www", "assets"]
  }
}

Configure headers to pass to the default static file server:

"buddy": {
  "server": {
    "port": 8000,
    "directory": "www",
    "headers": {
      "x-foo": "foo"
    }
  }
}

Specify an alternative root url from which to serve source maps:

"buddy": {
  "server": {
    "port": 8000,
    "directory": "www",
    "sourceroot": "https://raw.githubusercontent.com/user/repo/master/"
  }
}

Custom application server

To use a custom application server instead of the default, specify a file path to your server:

"buddy": {
  "server": {
    "port": 8000,
    "file": "./index.js"
  }
}

Configure environment variables with env:

"buddy": {
  "server": {
    "port": 8000,
    "file": "./index.js",
    "env": {
      "DEBUG": "*"
    }
  }
}

Configure flags to pass to the Node process running your server:

"buddy": {
  "server": {
    "port": 8000,
    "file": "./index.js",
    "flags": ['--inspect']
  }
}

NOTE The current port number will be exposed as process.env.PORT.