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

@vaporweb/component

v1.0.2

Published

## Component Scripts

Downloads

6

Readme

@vaporweb/component

Component Scripts

component build

Builds the project for production. CLI options will be forwarded to Rollup.

Rollup CLI options

Build files are output at the main and module paths set in the project's package.json file.

component develop

Builds the project in development mode and watches for changes. CLI options will be forwarded to Rollup.

Rollup CLI options

component lint

Runs the linter.

CLI options will be forwarded to eslint or tslint. For example, component lint --fix.

ESLint CLI options

TSLint CLI options

component test

Starts the test runner. CLI options will be forwarded to Jest. For example, component test --watch.

Jest CLI options

You can override jest configuration options by adding them to the package.json file.

Component Config

You can modify the config by placing a .component.js file in the root of your project. The config defaults are given in the example below.

  module.exports = {
    babel: true,
    eslint: true,
    tsc: false,
    tslint: false,
    rollup(config, { env }) {
      // here you can add additional plugins, e.g.
      // if (env === 'production') {
      //   config.plugins.push(terser())
      // }
      return config
    }
  }