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

code-gen-library

v1.0.9

Published

[![npm version](https://badge.fury.io/js/code-gen-library.svg)](https://badge.fury.io/js/code-gen-library)

Downloads

8

Readme

Code Gen Library

npm version

Stop worrying about the small things. A quick and opinionated way of generating code for your React projects 🏗


Installation

npm install --save-dev code-gen-library

Usage

npx generate

or if installed globally

generate

Once executed, The following message should appear

? [PLOP] Please choose a generator. (Use arrow keys)
❯ Component - Generate a React component ⚛️
  Util - Generate a util function 🛠

Default Options

1. React Components ⚛️

The CLI will ask you for the following information

Command | Description | Default value -- | -- | -- | -- Component name? | The name of your React component |
Do you want a separate file for styles? | If you want your styles to live outside the main component | ✅ Do you want a separate file for models | If you want your models to live outside the component of the folder | ✅

Example

If we choose the component name to be input text and everything else goes to default we end up with.

✔  ++ /path/to/your/repo/src/components/InputText/InputText.tsx
✔  ++ /path/to/your/repo/src/components/InputText/index.ts
✔  ++ /path/to/your/repo/src/components/InputText/InputText.styles.ts
✔  ++ /path/to/your/repo/src/components/InputText/InputText.models.ts

2. Utils 🛠

Command | Description | Default value -- | -- | -- | -- Util name? | The name of your util function |
What path shall we put it in? (src/utils) | The path in which the new folder is going to be added in | src/utils

If we choose the component name to be date format and everything else goes to default we end up with.

✔  ++ /path/to/your/repo/src/utils/dateFormat/dateFormat.ts
✔  ++ /path/to/your/repo/src/utils/dateFormat/index.ts

Customising

Right now you might be wondering.

What if I don't use TypeScript? What if I don't want to be asked every time if styles should be separate files? ...

All of these are very valid concerns and part of the reason why I decided to make this library. For those of you who want more customisation, a config file can be added with your preferences.

Create a cgl.config.js file on the root of your repo.

Here is some more information about what can be customised

Customisation Options

Rule | Description | Default value -- | -- | -- componentsPath | The path where the components will be put | src/components/ jsx | If the main component will be .jsx / .tsx or .js / .ts | true utilsPath | The default path for the utils | src/utils/ withModels | Models to be separated from the main component. Models files will suffix with .models.* | true withStyles | Styles to be separated from the main component. Styles files will suffix with .styles.* | true withTests | File for tests to also be included in the same directory. WIll suffix with .test.* format | true withTypescript | All files will be generated with TypeScript .ts / .tsx format | true

Inspiration

Check out this link for reasoning and inspiration behind code-gen-library

More to come soon