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

dg-reacting

v1.0.1

Published

Run build with a command ```sh npm run build ``` You must upload these folders/files: index.html dist/ static/ examples/ (local versions of API JSON files)

Downloads

2

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

ryanscottaudioryanscottaudio

Keywords

Readme

Build

Run build with a command

npm run build

You must upload these folders/files: index.html dist/ static/ examples/ (local versions of API JSON files)

Prerequisites

To test Nanit web app you need to have the following tools installed

  • Node.js min. v4.0
  • Bower
  • NPM (in most cases installs with Node.js)
  • Gulp

Navigate to project root with terminal (where package.json is located) and run

$ npm install --no-progress

Running the app

After installing everything, navigate to project root with terminal and run

$ npm start

Then you will see a message

Listening at http://localhost:3016

Navigate to localhost:3016 in your browser

Folder structure

Folder structure and workflow based on Redux framework:

  • actions
  • components
  • containers
    • ...
  • helpers
    • ...
  • reducers
    • ...
  • routes
    • index.js
  • store
    • index.js
  • index.js
  • index.html
  • package.json

API endpoint and general configuration

All project configuration including API endpoint is in webpack.config.js. Change content of ROOT constant and restart webpack server or build again. Beware that all content must be wrapped in JSON stringify method.