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

component-helper

v1.3.1-rc.1

Published

Create, build, test, serve and release small and large projects quickly

Downloads

6

Readme

Component Helper NPM version Circle CI

Create, Build, Test, Serve and Release. Quickly

Installation

npm install -g component-helper

Quick Start

Creating A New Component

To create a new project with a build process, tdd and continuous deployment already set-up

  1. Run component new *component-name* (which will create your component directory)
  2. follow on-screen instructions.
  3. Run npm start within your new directory

More Info >

Enhancing An Existing Project

Get the CLI (build, test, release etc) working within an existing project

  1. Copy the component.config.js into your project root
  2. Remove and Update the the config for your needs
  3. Update the paths object to match your directory structure

Use Cases

API

The component helper can be run from the command line or directly from within NodeJS files (i.e. a gulpfile). The tasks are almost exactly the same.

Once required (var component = require('component-helper');), you can call the following:

CLI | Node --- | ---- component new component-name | unavailable component build | component.build.run(replacements) (optional: replacements object) component build scripts | component.build.scripts() component build styles | component.build.styles() component build html | component.build.html(replacements) (optional: replacements object) component build server-config-files | component.build.serverConfigFiles() component serve | component.serve.run(config) (optional: server config) component serve path/to/serve | component.serve.adhoc(path) (mandatory: path/to/serve) component test | component.test.run() component test tdd | component.test.tdd() component init bower | component.init.bower() component init git | component.init.git(repository) (mandatory: Git URL) component bump Semantic Version | component.bump.run(versionType) (optional: major, minor, patch, prerelease or semantic version) component release Semantic Version | component.release.run(versionType) (optional: major, minor, patch, prerelease or semantic version) component release gh-pages | component.release.ghPages(message) (optional: commit message) component release s3 | component.release.s3(version) (optional: semantic version)

The CLI and Node will use the config set within component.config.js in your project root.

Contributing to the Helper

This project depends on collaboration between developers. Contributions of any size are actively encouraged.

Read More >