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

@caruuto/cdn

v4.0.0

Published

- [Overview](#overview) - [Requirements](#requirements) - [Your First CDN Project](#your-first-cdn-project) - [Links](#links)

Downloads

5

Readme

CDN

Overview

Requirements

  • Node.js (supported versions: 6.9.2, 6.11.1, 8.9.4)

Your first CDN project

Install dependencies

Install CDN

$ cd my-app
$ npm install @caruuto/cdn

Add an entry point

You'll need an entry point for your project. We'll create a file called index.js and later we will start the application with node index.js. Add the following to the new file:

/**
 *  index.js
 */
const app = require('@caruuto/cdn')

Start the server

CDN can be started from the command line simply by issuing the following command:

$ node index.js

With the default configuration, our CDN server is available at http://localhost:8001. Visiting this URL will display a welcome message.

Configuration

CDN requires a configuration file specific to the application environment. For example in the production environment it will look for a file named config.production.json.

When CDN was installed, a development configuration file was created for you in a config folder at your application root.

Run CDN as a service

To run your CDN application in the background as a service, install Forever and Forever Service:

$ npm install forever forever-service -g

$ forever-service install -s index.js -e NODE_ENV=production cdn --start

Note: the environment variable NODE_ENV=production must be set to the required configuration version matching the configuration files available in the config directory.

Configuring an image source

Before you can serve assets or images you need to tell CDN where your files are located. Currently, CDN can serve your files from three types of source: Amazon S3, a remote server, and the the local filesystem. We'll start using the local filesystem, but see the full documentation for details on using the other source types.

The sample configuration file defines a local filesystem source. The path property is set to use an directory called images at the root of your application. CDN will look for your files at the location defined in this path property every time it handles a request.

Example

{
  "server": {
    "host": "127.0.0.1",
    "port": 8001
  },
  "images": {
    "directory": {
      "enabled": true,
      "path": "./images"
    }
  }
}

We'll use the above configuration for an example. With image files in the images directory we can make a request for one to view it in the browser:

Images available
$ my-app/images  ls -la
total 9464
drwxr-xr-x  4 root  wheel      136 13 Mar 13:02 .
drwxr-xr-x  4 root  wheel      136 13 Mar 13:01 ..
-rw-r--r--  1 root  wheel     9396 13 Mar 13:02 92875.jpg
-rw-r--r--  1 root  wheel  4832710 13 Mar 13:02 92876.jpg
Browser request

http://127.0.0.1:8001/92875.jpg

Links