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

generator-asimov-component

v0.0.28

Published

A generator for Yeoman

Downloads

32

Readme

generator-asimov-component Build Status

A generator for Yeoman.

Getting Started

Installing Yeoman?

Not every new computer comes with a Yeoman pre-installed. He lives in the npm package repository.

$ npm install -g yo

Installing the Asimov component generator

To install generator-asimov-component from npm, run:

$ npm install -g generator-asimov-component

Building your first component

Since every every Asimov component is expected to be a standalone repository we recommend starting by creating your repository and checking it out locally.

Next go into the folder you just checked out and initiate the generator:

$ yo asimov-component

You'll be promtped to answer a couple questions to help us generate your component. These questions are explained below:

What is the name of your component?

A short name for people to find your component among other things eg. fluid grid, modal, awesome forms etc.

A short description?

A short description for people who might be looking to use your component eg. A simple grid for Asimov projects etc.

Is this component maintained by the asimov team?

Is this component being developed on behalf of the Asimov core team. You should almost always answer no.

Should this component conform to offical packages?

Do you wish for your component to be held to the same strict coding standards as officially maintained packages. If you answered yes to the previous question you will not be asked this.

Will this component be IE8 compatible?

Do you wish for Asimov's internal code quality checks to alert if something may not work in IE8. This is by no means a silver bullet so be sure to test your components :) If you answered yes to the previous question you will not be asked this since all official packages enable this.

Will this component have js?

This needs to be true if your component has javascript otherwise project using this component wont get your javascript.

Is this component private?

Say yes if you want to keep the package private and do not want to register the bower package in future.

The generator will now create the directory structure required for Asimov components as well as basic package.json and bower.json files.

Next you will need to initialize npm

npm init

You should able to accept the defaults values unless you wish to change them. We recommend changing the license to MIT.

You're now ready to start building your component!

License

MIT License