Skip to content

Suggestion to use existing CLI #122

Description

@coolassassin

Hello, everyone!

I see that you are trying to create a great product and I can see that you have made a nice logo and really great website for your tool.
I have been on your place few years ago, and same as you did my own CLI to generate components

There are many tools like that:

  • plop
  • hygen
  • yeoman

It is can be a bit tricky to be better in just generating components, any content to be precise.
But I did my own CLI because I have wanted to support updates. It is great to generate component, but what is more great - is add a story or test to component with CLI, just based on existent folders and files.

And I have already done CLI like that. You can check it, it calls reactcci.
More then that, I have moved forward and modernized it with VSCode extension, because somewhen it is easier to make few clicks and got result.

So... What am i doing here then... I just wanted probably to ask you, what needs did you cover by your CLI, which can't be closed with mine. And also, I want to welcome you to become an author or at least idea maker for my CLI.
I have integrated my CLI to many products and it showed itself very well. But maybe your product has special needs, which you have tried to cover with your product.

Let me know if you have something like that, and I am very welcome to see you in my project and user or as contributor.

Good luck!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions