99x / react-scaffolder Goto Github PK

• Do not require cli param name for generated file and use "index.js" by default

I think about to use some JS template engine to generate files. To easily add some new templates for this project.

Replace react-boilerplate (code generated with init command) with create-react-app boilerplate.

Create benchmark against clearly defined performance criteria to test performance of code.

Port code to es6 with babel

expected behaviour

According to the documentation it should create a new project from this command
react init projectname

steps to reproduce the problem.

It gives this error on CLI

isuruAb:github isuruAb$ react init awesome-project
env: node\r: No such file or directory

specifications like the version of the project, operating system, or hardware.

macOS Sierra 10.12.5

Create descriptive documentation for usage.

Areas to discuss

• What will be the future of react-scaffolder.
• What features that needs to included.
• Enhancements on existing features.

Add configuration options for .reactclirc file.

Actual Behaviour

After last PR there is no ability to generate files without folders.

Generate prop-types within a component with the CLI itself.

expected behaviour

After running

npm install -g react-scaffolder
react v -c

I get the error

env: node\r: No such file or directory

steps to reproduce the problem.

See above

specifications like the version of the project, operating system, or hardware.

I'm running [email protected] and [email protected] on [email protected]

• It is a bit confusing when we have two names in npm and github.
• Developer community is well adjusted to use the name cli for scaffolding tools

• Do not use "components" folder. Some projects can use other structure (for example: src/pages) Move that to the .reactclirc
• Rename "parent and child" to "Class" and "Function" or "Stateless" as in react docs
• Update exist templates and add new (for example use proposal class properties and redux)
• Better validation for prop names (not empty and not starts from space or number)
• Do not ask question "Add propTypes" if you set at .reactclirc that you always use propTypes

Expected Behaviour

add test cases for missing functions

Would you like to work on the issue?

yes

Add .editorconfig to maintain consistent code style. 🌍

editorconfig

Focus
We need to look into why this hasn't reached to developer community yet.

NPM Stats
0 downloads in the last month

https://www.npmjs.com/package/@99xt/react-cli

Actual Behaviour

readme doesn't contain anything about clone from github feature.

Expected Behaviour

Update readme file.add about clone from repo feature.

Would you like to work on the issue?

yes

And as CONTRIBUTING.md says "Clarify the issue or the feature that's going to be implemented"

• Add default config if user don't have ".reactclirc"
• Count props, don't ask user about a number
• Remove filename postfix ".react.js"

Also maybe I'll add some features for redux.

I do not agree with name like parent or child, but I like format that you use to store templates and interactive cli.

Define propTypes with type in propNames input (name:type)

Generate files like that and also without namespace before the slash.

Improve error messages in case of exceptions.

• Trying to use an existing directory name to create a project.
• Overwriting existing file names.

I think that it would be better to use object as argument.
instead of

generate.prototype.createComponent = function(
    module,
    componentName,
    answers,
    answersInner,
    onlyFile, 
    cb
) {}

better is

generate.prototype.createComponent = function({
    module,
    componentName,
    answers,
    answersInner = null,
    onlyFile = false, 
    cb
}) {}

And later use that:

generate.createComponent({
    module: modulename,
    componentName: name,
    cb: function(status) {}
});

follow popular quick starters

Configure and rewrite unit tests with Jest.

Steps 1.
What are the useful react templates dev community is interested in?

• Redux based
• fluxible based boiletplate

Step 2.
Create Github projects and start implementation

Add pull request template and issue template

expected behaviour

Using latest (Compatible) versions of npm packages

steps to reproduce the problem.

N/A

specifications like the version of the project, operating system, or hardware.

N/A

This is related to future work. Objective is to create an entire eco system of clients depending on a core set of APIs provided by react-scaffolder.

According to the proposed architecture core APIs will moved into a separate package. Probably similar to react-scaffolder-core.

Core will be consumed by client application. Web client, CLI, Electron application, opening up numerous possibilities rather than sticking into a CLI based solution.

Proposed architecture:

Add CODE_OF_CONDUCT.md

Design a logo

If user define prop name with * at the end (name*) set ptopType as required

expected behaviour

√ application created successfully

steps to reproduce the problem.

Install react-scaffolder globally and run react init myApp

specifications like the version of the project, operating system, or hardware.

v0.3.0

fix

The error occurs because in bin/initialize.js at rule 14 init is declared without the let/const/var keyword. I've changed it to var and it worked fine.

Currently boilerplate is generated based on a custom boilerplate. This should be customizable by adding the option to initialize the project based on a boilerplate on GitHub.