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

init-fc

v0.1.0

Published

![Cover image](https://i.imgur.com/BP7MLMx.gif)

Downloads

4

Readme

⚛️ Init-FC - Create a new React component

Cover image

Installation

npm i -g init-fc

This is a Node.js script that helps developers create a new React component. When executed, it prompts the user for information about the component to be created, such as its name, type, and whether it requires Scss styles or not. It also allows the user to extend an existing base component (div, button, input, or span).

The script imports several Node.js modules and external packages such as @clack/prompts, fs-jetpack, and Handlebars. It then reads several templates files (types.hbs, styles.hbs, and component.hbs) and compiles them using Handlebars to generate the required code for the new component.

The script uses the current working directory to determine the location of the component to be created. It also reads a crcpaths.json file in the current working directory to determine the folder structure of the components in the project. If the file does not exist, it creates a default folder structure with atom, molecule, organism, template, and page folders.

After getting the required information from the user, the script creates a new folder for the component and generates the necessary files (types.ts, module.scss, index.ts, and tsx). It also exports the new component in the index.ts file of its respective component type folder.

Finally, the script displays a confirmation message indicating that the component has been successfully created.

You dont use atomic design?

If you don't use atomic design, you can create a crcpaths.json file in the root of your project with the following content:

{
  "locations": {
    "components": "src/components",
    "pages": "src/pages"
  }
}