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 🙏

© 2026 – Pkg Stats / Ryan Hefner

fepm

v1.1.2

Published

Simple front-end package copier for node.

Downloads

14

Readme

fepm

Simple front-end file manager for node.

It can be used with front-end files installed using npm, as a bower replacement.

Install it by:

npm install fepm -g

Check the frontend-package-example.json file for an example on how to setup multiple environments.

Here's a quick explanation of some of the properties:

/output

This is the output directory for all the environments.

/environments/name and /environments/default

name: name of the environment, should be the same as the environment variable ENV. default: if

default = true

this environment will be used even if not ENV variable is set.

/environments/configuration/packages

Here, we list all the packages we want to process. The "name" here will be used as output directory for the package. So if:

/output = "dist"

and

name = "jquery"

all the "files" listed in this package will go into:

./dist/jquery.

Note the property "outputName" for each file will be used as destination name. So in above example, if

outputName="jquery.js"

we will have the "source" file copied in:

./dist/jquery/jquery.js

Action is not implemented yet.

Note, in order to run it: fepm will execute using the frontend-package.json in your current directory.

Or you can do: fepm filename.json if you have multiple files for example.