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

@aramtech/verde

v1.3.4

Published

a CLI tool for vendoring utilities.

Downloads

596

Readme

verde

a CLI tool for vendoring utilities.

Project goals

  • To make it easy to vendor and share code between projects without having to resort to a full fledged package management solutions.
  • To allow the user to control where the code is hosted and how it's fetched, synced and versioned.
  • To support hot patches and changes to the code on the fly.

Installation

To install verde use npm and run the following command

$ npm i [email protected]:aramtech/verde.git --global

This will install verde from this github repository, you can then test it via:

$ verde list

no tool found!.

Vendoring

To turn a directory with TypeScript/JavaScript modules into a vendored utility run:

$ verde init <utility-name> -d [description]

This will create a utils.json file, which is a simple config file that contains:

{
    "name": "<utility-name>",
    "version": "0.1.0",
    "hash": "(a hash of the contents of all files of the utility)",
    "private": true,
    "description": ""
}
  1. name: The name of the utility.
  2. deps: The dependencies of the utility.
  3. version: The utility's version.
  4. private: Whether the utility is private to this project.

You can list the utilities in a given project by running:

$ verde list

* [email protected] | Utilities for manipulating with strings
* [email protected] | Utilities for integrating with odoo *private*

You can remove a utility from your project by running:

$ verde remove string-utils

[email protected] Was removed successfully

You can push a utility to github by running:

$ verde push string-utils

[email protected] Was pushed to github successfully

You can pull a utility from github by running:

$ verde pull string-utils

[email protected] was added to the project successfully

You can make a utility private by running:

$ verde hide string-utils

You can make it public again by running:

verde reveal string-utils