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

ber

v0.0.14

Published

Best ever resolver - local folders as package repository

Downloads

35

Readme

ber

npm i -g ber

Description

This tool allows to install package as local dependency using tarbal (npm pack).

Usage

ber i path_to_package

ber i // updates all local packages

Packages are stored as tgz files in folder ./local_modules

Primary it is used to deploy functions to firebase with local packages

Go to example directory (example) and run:

cd ./libs/lib_a
ber i ../libs/lib_b // install lib_b in lib_a
cd ../../web // go to web
ber i ../libs/lib_a
ber i ../libs/lib_b

Example directory has dependency tree:

  • web (depends on lib_a, and lib_b)
  • lib_a (depends on lib_b)

No whenever something changes, just hit in web directory ber i And everything will be reinstalled

ber, will first build package lib_b (execute build script if any, and pack the package), then build package lib_a, and then install them both in web using npm install ./.local_modules/*.tgz