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

vpartlist

v0.1.7

Published

build a parts list for a verilog module

Downloads

16

Readme

vpartlist

Build Status

build a parts list for verilog module

example.js

var vPartList = require('./lib/vpartlist'),
    path = require('path');

var res = ["./sample_a/", "./sample_b"],
    des = "./sandbox/example",
    mod = "./sample_a/shifter/shifter.v";
   
new vPartList(path.resolve(mod), {
    path: false,
    repositories: res,
    output: path.resolve(des),
    verbose: true //should see some output in terminal
}, function(mod, err) {
    console.log(mod);
});

Output

{ name: 'shifter',
  partlist: 
  [  'shifter.v',
     'shifter_level_0.v',
     'shifter_level_1.v',
     'shifter_level_2.v',
     'shifter_level_3.v',
     'shifter_lsb_msb.v',
     'mux4_1.v',
     'mux2_1.v',
     'not1.v',
     'nand2.v' 
  ] 
}

methods

  vPartList(component, opts, callback, undefined)
  Build a part list for a component
  @param  String   component fullpath/to/module.v
  @param  Object   opts      {
                                 "repositories": undefined,
                                 "output": undefined, //NOPE
                                 "path": false,
                                 "verbose": false
                              }
  @param  function callback  (result, err){
            @err = {name: PError, message:, stack:,}
            @result = {name:, partlist:,}
          }

usage

This package also ships with a vpartlist command.

usage: vpartlist sample_a/alu/alu.v -vr sample_a/ sample_b/ -o sandbox/foo 

  build a parts list for `alu.v` module from components found under [sample_a/, sample_b/]
  and save all components to `sandbox/foo` (create dir if not existed)

FLAGS:
  -h, --help    help
  -r repoDir/, --repositories=reporDir/   root directories of verilog source code 
      (DEFAULT to parent directory of requested module, e.g sample_a/alu/ for sample_a/alu/alu.v)
  -o dir/, --output=dir/  output directory
      (DEFAULT no output if undefined)
  -v, --verbose verbose log
  -p, --path    include full path to each components

install

With npm do:

npm install vpartlist --save

to get the library, or

npm install -g vpartlist

to get the command.