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

roderic

v0.0.1430

Published

[![npm version](https://badge.fury.io/js/roderic.svg)](https://badge.fury.io/js/roderic) [![Build Status](https://travis-ci.org/stopsopa/roderic.svg?branch=master)](https://travis-ci.org/stopsopa/roderic)

Downloads

10

Vulnerabilities

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

Links

Maintainers

stopsopa-ownerstopsopa-owner

Keywords

webpackreactredux

Readme

npm version Build Status

INSTALL

npx roderic
    # default directry is roderic-project
npx roderic directory
npx roderic .

DEV

mkdir roderic_development
cd roderic_development
git clone [email protected]:stopsopa/roderic.git lib-npm-link
cp lib-npm-link/dev/* .    
(cd lib-npm-link && yarn && npm link)
roderic
(cd roderic-project/react && yarn)
(cd roderic-project/react && npm link roderic)    
ls -la roderic-project/react/node_modules/ | grep roderic

Now last command ...

ls -la roderic-project/react/node_modules/ | grep roderic

... should return (roderic lib should be symlink in node_modules):

lrwxr-xr-x    1 sd  staff      58  2 Aug 12:44 roderic -> ../../../../../../../../usr/local/lib/node_modules/roderic

And finally you can just manipulate both directories (lib-npm-link & roderic-project). I you like save changes of lib-npm-link then run:

make u

I you want to safe changes from roderic-project then run:

make b

then commit changes in lib-npm-link and run again

make u

To test installation process and if everything works after run:

sudo make t

There is another version of update script. Use it when you already pushed changes to git:

(cd lib-npm-link/ && make update-force)

summary

  • test.sh - use when you want to test installation process (might be unsafe - it might override changes in unsafed roderic-project directory)

  • back.sh - use when you want to include to library changes from temporary installation (safe)