npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

react-juno

v1.1.8

Published

A CLI tool for bootstrapping react projects with tailwind css

Downloads

336

Readme

React-juno

npm npm npm

react-juno is a command-line tool to bootstrap a new React project with Vite and Tailwind CSS. This tool allows you to quickly set up a React project with essential configurations like Redux, React Router, ESLint, Prettier, and Jest for testing.

Features

  • Vite for fast build and development.
  • Tailwind CSS for styling.
  • Redux for state management (optional).
  • React Router for routing (optional).
  • ESLint for code linting (optional).
  • Prettier for code formatting (optional).
  • Jest and React Testing Library for testing (optional).
  • Creates a well-structured project directory.

Installation

To install the CLI globally, run:

npm install -g react-juno

Usage

After you have installed the react-juno cli globally ,run this command to create a project

react-juno init <projectName>

After the initialization the project structure will look like this

my-new-project/
├── node_modules/
├── public/
├── src/
│   ├── components/
│   ├── contexts/
│   ├── pages/
│   ├── redux/
│   │   └── store.js
│   ├── routes/
│   │   └── AppRouter.js
│   ├── styles/
│   │   └── global.js
│   ├── utils/
│   ├── index.css
│   ├── App.jsx
│   └── main.jsx
├── .eslintrc.js
├── .prettierrc
├── jest.config.js
├── tailwind.config.js
├── package.json
├── package-lock.json
└── README.md

Contributing

We welcome contributions to the react-juno cli If you would like to contribute, please follow these steps:

1. Fork the Repository:

Click the "Fork" button at the top right corner of this repository to create a copy of the repository in your GitHub account.

2. Clone Your Fork:

Clone your forked repository to your local machine.

git clone https://github.com/headrickleonard/react-juno.git
cd react-juno

3. Create a Branch:

Create a new branch for your feature or bugfix.

git checkout -b feature/your-feature-name

4. Make Changes:

Make your changes in the new branch.

5. Commit Your Changes:

Commit your changes with a descriptive commit message.

git commit -m "Add new feature: your-feature-name"

6. Push Your Changes:

Push your changes to your forked repository.

git push origin feature/your-feature-name

7. Create a Pull Request:

Open a pull request to the main repository, explaining your changes and the feature or bugfix you have implemented.