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

gpeto

v0.3.1

Published

<h1 align="center"> <img src="images/logo-mini.png"> </h1>

Downloads

6

Readme

Problem

I was working on a project using the bootstrap when I needed to style a progress bar. I created a new file and rewrote the entire bootstrap style for my new progress bar. Then I thought, what if I could copy the progress of the bootstrap quickly and use the styling source for me. Then the gPeto emerged, continue reading to learn more.

Introduction

Progress

You most often don't use all the components that a framework or tool contains.

With gPeto, you can install only what you'll need or install it on demand.

Getting started

Installation

npm install -g gpeto

Add a project for gPeto

With gpeto's command in your terminal , the first thing that you need to do is download the project wich you'll modularize (in this example we'll use Bootstrap).

bower install Bootstrap

cd bower_components

We'll add the Bootstrap to our gpeto folder.

gpeto add bootstrap
# [gpeto] ➜ Copied bootstrap successifuly! ⌚ 96 ms

Installing a component in your project

You can go to the project what you're working on and install only the components you need.

gpeto install bootstrap/less/progress.less
# [gpeto] ➜ Copied bootstrap/less/progress.less to gpeto_components ⌚ 53 ms

If you don't specify a folder with the --out flag, all components will be installed in gpeto_components folder.

Avaliable commands

Commands:

  • install
  • uninstall
  • add
  • remove

Flags:

  • --out - -o
  • --vesrion - -v
  • --help - -h

Caution

gPeto doesn't install dependencies automatically yet, but I'm working on some way of doing that.

Contribute

Your contributions and suggestions are :heart: welcome.

Todo

  • [x] Add remove and uninstall commands
  • [ ] Install dependencies automatically

License

MIT © Filipe Linhares