React CodeGen CLI

React CodeGen is a development tool to quickly generate React components. It helps you to speed up productivity in React projects and stop copying, pasting files.

Get Started · Report Bug · Request Feature

Installation
Get Started
Configuration File
Configuration Options
Roadmap
Contributing
License

Installation

To install the latest version run the following command:

npm i react-codegen-cli --save-dev

React CodeGen lets you setup everything by simply running the following command:

npx react-codegen-cli init

Question by question, it will guide you through the whole process of setting up a configuration file, selecting stylesheet format, picking a destination of generated files, and a lot more.

Get Started

The following command can be used to generate code:

npm run react-codegen

After running the command in the terminal, you can enter the name of the component and configure the generation of the files. When creating a React component, you are given the choice to modify the component parts, such as connecting the useState, useEffect, propTypes and so on.

Configuration File

You also can set-up configuration file manually. React CodeGen uses cosmiconfig for configuration file support. This means you can configure it via:

A "react-codegen" key in your package.json file.
A .react-codegenrc file, written in JSON or YAML, with optional extensions: .json/.yaml/.yml (without extension takes precedence).
A .react-codegenrc.js or react-codegen.config.js file that exports an object.

react-codegen will look for a configuration file in root folder and use it if available. If no config file found it will fallback to a default configuration.

Configuration Options

Type	Value	Default	Description
styles	string	scss	Stylesheet format
typescript	boolean	false	Generate typescript files
jsxExt	boolean	true	Use `jsx` extension for components
newJsx	boolean	false	Remove react from scope (use new JSX transform)
fileNameCase	came, pascal, snake, snakeUpper, kebab	pascal	File name case for generated files (default: `MyComponent.jsx`)
path	string	src/components	Path to generate files
wrapFolder	boolean	true	Create a wrap folder for generated files
cssModules	boolean	false	Generate css module
exportType	default, named	default	Export type to be used for modules
arrowFunction	boolean	true	Use arrow functions insead of regular

Example:

{
  "styles": "scss",
  "typescript": false,
  "jsxExt": true,
  "fileNameCase": "pascal",
  "path": "src/components"
}

Roadmap

See the open issues for a list of proposed features (and known issues).

Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

Fork the Project
Create your Feature Branch (git checkout -b feature/amazing-feature dev)
Commit your Changes (npm run commit)
Push to the Branch (git push origin feature/amazing-feature)
Open a Pull Request

License

React CodeGen CLI is open source software licensed as MIT.

The automated release is failing 🚨

🚨 The automated release from the `next` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the next branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

vs-cristian / react-codegen-cli Goto Github PK