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

sepharad

v0.0.2

Published

Visualize the JS module dependencies from your Source Code in Github

Downloads

5

Readme

sepharad

Visualize the JS module (AMD or CommonJS) dependencies from your Source Code in Github.

Sepharad is built on top of dependo (https://github.com/auchenberg/dependo#introduction). The reason Sepharad was built was to overcome the limitation of dependo, which is that; the source code must be in the local file system to generate dependencies. Sepharad overcomes that limitation by enabling visualization of JS dependencies from source code located in remote Github.

Usage

  $ npm install dependo
var sepharad = require("sepharad");

// the below code generates a visualization report file 
// called report.html of kraken-js project's Javascript  
// files' dependencies present in the "lib/" folder 
// directly from github.

sepharad({
  url : "https://github.com/krakenjs/kraken-js",
  path: "lib/",
  format: "cjs",
  exclude: "^node_modules",
  output: "report.html"
});

API


    sepharad({
    	 "url"     : <github url for the source>, (required)
    	 "branch"  : <branch>, (optional and defaults to master)
    	 "path"    : <file/dir in the source code from where dependencies need to be visualized>, (required)
    	 "format"  : <format to parse (amd or cjs)>, (required)
    	 "exclude" : <a regular expression for excluding files>, (optional and default is none)
    	 "output"  : <file to save the generated dependency output html> (required)
    });

ToDo

  • write tests - mocha
  • make sephard independent of dependo
  • add a CLI feature for sepharad
  • grunt task for sephard