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

atomic-scripts

v2.1.2

Published

React Component Generator in Atomic-Design Manner

Downloads

42

Readme

atomic-scripts

Greenkeeper badge a small cli helper-tool for fast component scaffolding.

npm Build Status Coverage Status

Installation

  1. npm install --save-dev atomic-scripts or yarn add --dev atomic-scripts

  2. Update your package.json like this:

    {
      "scripts": {
    +   "atomic": "atomic-scripts"
      },
    + "atomic-scripts": {
    +   "componentsDir": "src/components/"
    + }
    }

Usage:

In your terminal start the cli-script via: npm run atomic or yarn atomic

The answer all the questions and the component will be scaffolded into the correct directory. atomic-scripts

Configuration

For custom componentTypes to choose in your cli: add them in your package.json config:

  "atomic-scripts": {
+   "componentTypes": [
+      "atom",
+      "molecule",
+      "organism",
+      "template"          
+    ]
  }
}

If you want to specify your own templates: configure the path of your own templates.js in the package.json config:

  "atomic-scripts": {
    "componentsDir": "src/components/",
+   "templates": "thePathToYour/templates.js"
  }
}

The specified templates.js MUST export an array of objects which contains two keys: fileName and fileContent.

These two can be strings or functions. If a function is supplied it will called with one parameter: an object with all user answers and must return a string.

Here is an example how this answers object could look like:

{
  type: 'atom',
  name: 'TestComponent',
}

For an quickstart look at the original templates.js file.

Created by

License

MIT © Michael Seel