v2.0.2

• Fixed issue with rhax dep. removing pipe() function
• Dependencies updates for security patches
• Disabled reportTelemetry by default

v2.0.0

Version 2.0 🚀🚀🚀

This version introduces a complete overhaul of Agrippa's internals, and a new docs website - agrippa.dev!
If you're coming from v1, you might want to take the tutorial there - the essence of using Agrippa is the same, but there are differences too.

Agrippa v2.0 takes the leap into framework-agnostic territory - instead of being a React CLI, it now supports React (& React Native), Preact and Solid.js!
Support for additional frameworks will be added soon; we currently have two on our sights - Vue.js and Svelte - as well as multiple other environments (Next.js, Astro.build, etc.). The same goes for other technologies - styling solutions, testing frameworks, etc.

The other big thing is a new Plugin system 🌟
It's still not completely refined, and will definitely require some more improvements based on user input, but this system will allow us to scale and expand functionality and support to basically anything, and will allow the community to create plugins for their own setups and tools.

This version has been in the works for a longgggg time. I'm so excited for this to finally be released!

As always, if you've found any bugs or want to suggest a feature or improvement, I'd love to hear you. The best way to do this currently is on my twitter or by opening a new issue.

Cheers!

v2.0.0 Release Candidate 1

First release candidate for version 2.0 🚀

This version introduces a complete overhaul of Agrippa's internals, and a new docs website - agrippa.dev!
If you're coming from v1, you might want to take the tutorial there - the essence of using Agrippa is the same, but there are differences too.

Agrippa v2.0 takes the leap into framework-agnostic territory - instead of being a React CLI, it now supports React (& React Native), Preact and Solid.js!
Support for additional frameworks will be added soon; we currently have two on our sights - Vue.js and Svelte - as well as multiple other environments (Next.js, Astro.build, etc.). The same goes for other technologies - styling solutions, testing frameworks, etc.

The other big thing is a new Plugin system 🌟
It's still not completely refined, and will definitely require some more improvements based on user input, but this system will allow us to scale and expand functionality and support to basically anything, and will allow the community to create plugins for their own setups and tools.

This version has been in the works for a long time. We will probably have a few bugs to sort out or edges to refine, but I'm incredibly excited to finally release version 2 to the public.

As always, if you've found any bugs or want to suggest a feature or improvement, I'd love to hear you. The best way to do this currently is on my twitter or by opening a new issue.

Cheers!

v1.4.0

Agrippa v1.4.0 is officially out!

To update, call npm i -g agrippa.
Please reach out with any bugs or feedback!

The new version introduces some cool new features:

• Agrippa's terminal UI has been revamped! hopefully you'll agree the new look is a lot more ✨aesthetic✨
  
  
• tsPropsDeclaration: TS users can now select between interfaces and types for component props declarations.
  For more info, see the docs on tsPropsDeclaration.
  Thanks for @spiftire for suggesting this!
  
  
• Styled-components: Agrippa now supports styling with styled-components! This is actually the second issue opened for Agrippa, and it's been open for quite a while now. It's truly nice to see it finally implemented. To check it out, use the value styled-components for the styling flag.
  Thanks for @hannanel100 for suggesting this!
  
  
• New post-command variables: two new variables, <ComponentName> and <component-name>, can now be used with post commands.
  The first is the generated component's name in pascal case (e.g. NiceButton), while the second is in kebab case (e.g. nice-button).
  
  
• Dependency cleanup: two packages that Agrippa has been using up to now, but hasn't really needed to, were removed, and Agrippa should now be a little lighter.

Also, more tests were added, which is always nice.

Cheers!

Full Changelog: v1.3.0...v1.4.0

v1.4.0 RC 1

Agrippa v1.4.0 has entered the RC stage!

This means it's almost ready for a production launch.
Assuming no bugs are found, it will be rolled officially in a few days.

To test out the new version, call npm i -g agrippa@next.

Please reach out with any bugs or feedback!

The new version introduces some cool new features:

• Agrippa's terminal UI has been revamped! hopefully you'll agree the new look is a lot more ✨aesthetic✨
  
  
• tsPropsDeclaration: TS users can now select between interfaces and types for component props declarations.
  For more info, see the docs on tsPropsDeclaration.
  Thanks for @spiftire for suggesting this!
  
  
• Styled-components: Agrippa now supports styling with styled-components! This is actually the second issue opened for Agrippa, and it's been open for quite a while now. t's truly nice to see it finally implemented. To check it out, use the value styled-components for the styling flag.
  Thanks for @hannanel100 for suggesting this!
  
  
• New post-command variables: two new variables, <ComponentName> and <component-name>, can now be used with post commands.
  The first is the generated component's name in pascal case (e.g. NiceButton), while the second is in kebab case (e.g. ice-button).
  
  
• Dependency cleanup: two packages that Agrippa has been using up to now, but hasn't really needed to, were removed, and Agrippa should now be a little lighter.

Also, more tests were added, which is always nice.

Cheers!

Full Changelog: v1.3.0...v1.4.0-rc.1

1.3.2

This version updates the version of follow-redirects in yarn.lock, following a security vulnerability discovered in some of its previous versions.

See https://huntr.dev/bounties/fc524e4b-ebb6-427d-ab67-a64181020406/.

v1.3.1

This patch version fixes a typo in the "new version" prompt.

v1.3.0

The third minor version of Agrippa is finally out!

This one was in the works for longer than the previous two versions; integration tests, in particular, were a challenge to implement.
The new version brings the following changes:

• The separate-index scheme: Agrippa's default component directories structure now consists of separate Component.jsx/Component.tsx, which contains the component logic, and index files, which make importing the component from outside less cumbersome. Previously, Agrippa placed the component logic under the index file, which resulted in less files overall but hurt the developer experience! Now the tool should be more fun to work with. Many thanks to @wickedpuppy for suggesting this feature!
  
  For more info, check out separate-index on Agrippa's docs.

• Support for React Native: Agrippa now supports React Native projects!
  Furthermore, it can auto-detect a react native project by having the react-native dependency in its package.json, so you don't really need to do anything different in a typical project! Of course, styling with React Native's StyleSheets is also supported (and enforced).
  
  For more info, check out reactNative on Agrippa's docs.

• Agrippa is now covered by integration tests, as well as more unit tests.
  Integration tests are a challenge - since Agrippa is all about reading and writing files automatically, testing it effectively requires setting up and running in a completely isolated environment! We ended up combining Docker, Jest and some custom code to create a pretty sophisticated solution, and it works quite well.
  More tests are on the way, but Agrippa already has pretty good coverage.

• Tweaks & Bug fixes:

  • props=ts can no longer be used without the typescript flag; additionally, the typescript flag now implies that props=ts (of course, this is overridden by any value set by the user).
  • The allowOutsideBase check is now skipped if baseDir is not specified.
  • Fixed a bug where --children would generate <div>children</div> instead of <div>{children}</div> in the JSX template.

To update, call npm i -g agrippa.

I'd like to welcome all of the new members of our community!
I'm delighted to see Agrippa growing as it has since its release, and super grateful towards everyone's contributions and support.

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.

Have a great weekend!

v1.2.1

This release fixes two small bugs from v1.2.0:

• The new version message was printed even when using the latest version
• When generating a component with no imports, a redundant empty line was generated at the top of the file.

To update, call npm i -g agrippa.

Your thoughts and feedback are most welcome.
If you've found a bug with this release, or want to suggest a new feature, please submit an issue.

Cheers!

v1.2.0

Agrippa is growing steadily - it's been out for a little over two months, and already has a small community around it! It makes me deeply glad, and I hope we can continue to grow this way.

These are the changes introduced in v1.2.0:

In general, the two main changes brought about are more options, this time with a focus on supporting different structural conventions that exist among React developers. Most notably, you can now:

• export a component as a default export (instead of a named export)
• declare a component as a function() declaration (instead of as a const with an arrow function)
• create memo() components.

These changes came as part of a larger reform in component generation. Generation logic was remade from the ground up - instead of a large, unwieldy template, we now have proper composition patterns and a ComponentComposer; internal terminology aside, this reform makes it much easier to scale, maintain and test the generation logic.

Following this reform, we have begun the process of writing standardized tests - testing for some of the core code already exists, and the rest will be covered in the soon future.

In parallel, we got some bonus enhancements:

• Agrippa now checks for a new version when it's run. It's there to make sure you're always using the best version of the tool!
• The self-closing <div/> that was used in the generated template was replaced with a standard <div></div>.
• The list of options for agrippa gen was moved to the wiki and rewritten - check out The Complete List of Generation Options.
• Added a CONTRIBUTING.md guide.

We already have some work in queue for v1.3.0 - we're currently looking into adding support for styled-components, React native Stylesheets and Mui 5 styling, writing more tests and more. If you're in need of any of these or other features, tell us about it by opening an issue or joining an existing discussion!

As always, if you find a bug in Agrippa or want to suggest a new feature, please reach out here or wherever.

Thanks for your time, have a great day!