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

react-modelling

v0.0.201

Published

A CLI that gives opinion to React!

Downloads

10

Readme

A CLI that gives opinion to React

This library is only preview at the moment Next.js and Sass support will be available soon

How to install?

npm i -g react-modelling

The problem

What is the problem in React? Your projects quickly and easily can become a trash. Disorganization reigns because there is no a main pattern to React. And in a big team? Nobody can understand that structure. And what about writing boilerplates to create components or router all the time? React Modelling solves all of these organization problems using the CLI.

Here are the proposed structure: under construction

src
└───domain - Non-reusable components
└───components - Reusable components
└───pages - Pages folder
└───routes - Routes folder
└───constants - Variables folder. e.g.: theme variable
└───utils - Utilities. e.g.: validators and formatters
└───styles - Global styles
└───assets - Assets folder. e.g: icons and images
└───@types - Typescript Interfaces and Types

Going ahead...

src
└───components
│   └───Header
│       │   index.tsx
│       │   styles.ts

or using modularization

src
└───components
│   └───Layout
│         └───Header
|             |   index.tsx
|             |   style.ts
|
|   └───Form
│         └───Input
|             |   index.tsx
|             |   style.ts
│         └───Button
|             |   index.tsx
|             |   style.ts

CLI Commands

You can use in your terminal, the aliases remod, react-modelling, react-m or r-m to call the React Modelling.

Configure project

To configure the project

remod init

After this you should execute yarn or npm install

Page

To create a new page

remod page <name>

or you can create inside a module

remod page <name> <module-directory>

Example:

remod page Login users/authentication

Components

To create a new component

remod component <name>

Use the flag -r to generate an reusable component and -u for a non-reusable component. By default reusable component will be created.

or you can create inside a module

remod component <name> <module-name>

Example:

remod component LoginError users/messages

Router

To create a new router

remod router --init