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

rnx-gen

v1.0.12

Published

Quickly generate resources like screens, components, hooks and more with boilerplate code

Downloads

247

Readme

rnx-gen

Opinionated resources generator for React Native

create screen example

Installation

npm i rnx-gen --save-dev

Usage

1. Generate files for a new screen with boilerplate code for each file

npx rnx-gen g screen UserProfile

Result:

src
   |-screens
        |-UserProfileScreen
            |-__tests__
                |-UserProfileScreen.test.ts
            |-UserProfileScreen.tsx
            |-UserProfileScreen.types.ts
            |-UserProfileScreen.styles.ts
            |-UserProfileScreen.constants.ts
            |-index.ts

Command options:

| Option | Descriptions | | ----------- | ---------------------------------------------------------------- | | --no-test | Do not create the tests folder and the test file | | --no-const | Do not create the constants file | | --no-style | Do not create the styles file | | --path | Custom path beginning with src (example --path=src/screens/auth) | | --keep-name | Use the resource name provided as an option without modification |

2. Generate files for a new component with boilerplate code for each file

npx rnx-gen g component AlertModal

Result:

src
   |-components
        |-AlertModal
            |-__tests__
                |-AlertModal.test.ts
            |-AlertModal.tsx
            |-AlertModal.styles.ts
            |-index.ts

Command options:

| Option | Descriptions | | ----------- | -------------------------------------------------------------------- | | --no-test | Do not create the tests folder and the test file | | --no-dir | Do not create a separate folder for the component | | --no-style | Do not create the styles file | | --path | Custom path beginning with src (example --path=src/components/cards) | | --keep-name | Use the resource name provided as an option without modification |

3. Generate a new hook file with boilerplate code

npx rnx-gen g hook profileData

Result:

src
   |-hooks
        |-useProfileData
            |-useProfileData.ts
            |-useProfileData.test.ts
            |-index.ts

Command options:

| Option | Descriptions | | ----------- | ---------------------------------------------------------------- | | --no-test | Do not create the test file | | --no-dir | Do not create a separate folder for the hook | | --path | Custom path beginning with src (example --path=src/hooks/data) | | --keep-name | Use the resource name provided as an option without modification |

4. Generate a new Redux slice with boilerplate code

npx rnx-gen g slice users

Result:

src
   |-redux
        |-slices
            |-usersSlice.ts

Command options:

| Option | Descriptions | | ----------- | ------------------------------------------------------------------ | | --path | Custom path beginning with src (example --path=src/redux/reducers) | | --keep-name | Use the resource name provided as an option without modification |

5. Set up Redux files (Redux toolkit) with boilerplate code for each file

npx rnx-gen redux

Result:

src
   |-redux
        |-slices
            |-appSlice.ts
        |-selectors
            |-appSelectors.ts
        |-rootReducer.ts
        |-store.ts
        |-store.utils.ts