agrippa VS Ink

I'm working on a huge new version for Agrippa, which is essentially an open source tool for generating frontend components without the boilerplate (kind of like supercharged snippets, but even greater 🤩). Seeing as Tailwind is already used in many teams today and it's only becoming more and more popular, I thought it could be beneficial to many if Agrippa had first-class support for it - and it's a great opportunity to learn more about a trending tool, too 😄

To get started with Agrippa, read the Getting Started guide or visit us on GitHub. Your thoughts and feedback, as always, are most welcome. If you've found a bug with this release, or want to suggest a new feature, please submit an issue.

For the complete list of options that Agrippa supports, see The Complete List of Generation Options on the wiki. For more info about baseDir, see Using baseDir and dest. Finally, for more info about post-commands, which are one of the main features that make Agrippa as flexible as it is, see The Post Command cookbook 🍲.

That's it! Agrippa has an ever-growing community around it, and I hope you'll join it too! To get started, visit Agrippa on GitHub.

So, thanks everyone! If you're not using Agrippa, join us! Get started here.

I'm asking because we want to implement styled-components support for Agrippa, the React CLI for component generation! In fact, it's the second issue opened on our GitHub repository!

If you're not using Agrippa yet, get started here. If you are using Agrippa, thanks for being part of the community! Let us know what you think about it, here or elsewhere.

NPM, Github, Dev.to.

About a month ago, the first production version of Agrippa was published, and I announced it in my first post on dev.to, Meet Agrippa, the React CLI for component generation. I was honored at the amount of positive feedback for the project (thank you all!!), and had immediately started working on improving the tool further.

I've always wanted to build a CLI tool, and when I realized that you can build one using React with Ink, I converted my Python script into a CLI tool.

⚠️ Git for Windows Terminal is currently not supported, and the tool is limited to ink. We will look for alternatives later. Please use CMD, Vscode terminal's Git... terminal

There is a good solution for some of those cases - ink. With ink, I can implement text-based UI with knowledge of React, which is neat but there are still some caveats for my usages:

Looks cool, right? Building a similar UI in the terminal without any library would be quite hard, though, thanks to Ink it's almost as easy as building any frontend UI with React.

ink?

I'm writing a CLI with ink. Writing async code is important as to not block the rendering and respond to user input. I have a few loading animations that update every 100ms. Synchronous operations can make the animation hang for >500ms, making the animation choppy.

You get the comfort of using react components instead of fighting with HTML tables to make your emails look nice. I think it's awesome! It's analog to what ink[0] does with CLI outputs. Sure, you could write fancy CLI outputs in bash, but ink takes the pain out of it and makes it easy.

[0] https://github.com/vadimdemedes/ink

Due to Node's asynchronous behavior, it makes Node great for long-running processes that make a lot of HTTP requests, database calls, and other async ops, like a web server or a REST API. However, if I am making a CLI tool for pretty much personal use only, with very minimal async operations, then blocking the event loop with a synchronous function that will resolve almost immediately will make no difference perceivable to a human brain or have any speed benefits that someone can actually observe (think `fs.readFileSync` or `require('dotenv') of 10 line config file, or a quick embedded db (sqlite) query with only ~100 records. I'm wondering what the best way to implement the database part of the app synchronous. I can read/write to JSON files but it would be tricky because the data is relational, and some complex joins and other data wrangling operations are required (complex to perform in JS but are easy to implement in a SQL statement). It's not important what the operations are, that's not the point of this post. This is mostly a personal project of interest: making this CLI tool completely avoiding any async operations/using no promises. I would like to use node tho, as I said this is just out of interest and I also want to experiment with several CLI libraries such as Ink or Cliffy.