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

aacm

v1.0.5

Published

React faster.

Downloads

10

Readme

aacm

aacm makes components and styles for you.

Installation

aacm is meant to be installed globally, then used from your app's src/ directory (or equivalent).

$ sudo npm i -g aacm


Syntax

aacm [flags] <ComponentName>

For example,

aacm ItemDetail

gives you...

./components/ItemDetail/ItemDetail.jsx

import React from 'react';

import './ItemDetail.scss';

function ItemDetail() {
  return (
    <div className="ItemDetail">

    </div>
  );
}

export default ItemDetail;

and

./components/ItemDetail/ItemDetail.scss

.ItemDetail {
    
}

Now multiply that by every component you'll ever create and you've saved yourself some time. =)


Multiple Components

You can pass in multiple component names at once, like so...

aacm Thing1 Thing2 Thing3

This creates...

./components/Thing1/Thing1.jsx
./components/Thing1/Thing1.scss
./components/Thing2/Thing2.jsx
./components/Thing2/Thing2.scss
./components/Thing3/Thing3.jsx
./components/Thing3/Thing3.scss

according to the flags.


Flags

|Flag | Effect | | ---------------- | ---------------------------------------- | | -c, --class | Generates class components | | | Uses modern syntax | | -f, --functional | Generates functional components | | | This is the default | | -h, --help | Shows available flags | | | | | -i, --asi | Confidence Mode | | | Use Automatic Semicolon Insertion | | -k, --kebab | Makes the generated directories | | | and file names use kebab-case | | -V, --version | Shows version number | | | | | --css | Generates CSS | | | (default is SCSS) | | --old-class | Generates class components | | | Uses classic syntax | | --features | Outputs to features/ | | | (default is components/) |

Any of these may be combined.

For example, aacm ItemDetail -ik generates

./components/item-detail/item-detail.scss

and

./components/item-detail/item-detail.jsx (semicolon free).