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 🙏

© 2026 – Pkg Stats / Ryan Hefner

react-ts-cdk

v1.0.4

Published

React + Typescript Boilerplate

Downloads

10

Readme

react-ts-cdk

🔥 React + Typescript Boilerplate to develop your own react components and reuse in another projects

React Typescript Component Development Kit

Motivation

Components are cool! We should use them everywhere. So, you expent time developing a lot of components and now you want to reuse them in another awesome project & all your projects need your components updated when a new feature is released (and you also need typechecking, tests, hot module replacement & all the good stuff).

Directory Structure

.
├── src
|   └── components
|       └── MyComponent                 # Your component
|           ├── MyComponent.story.tsx   # Storybook of your component
|           ├── MyComponent.test.tsx    # Jest + Enzyme tests
|           ├── MyComponent.tsx         # Its JSX + Typescript file
|           ├── MyComponent.types.ts    # Types for props
|           └── index.ts                # Export Component
|       └── MyComponentX                # Another component X
|       └── MyComponentY                # Another component Y
|       └── MyComponentZ                # Another component Z
|       └── stories.tsx                 # Storybook config file
├── dist
|    └── index.js                       # Exporting all Componentss

Usage

  1. Fork it!
  2. install dependencies:
yarn install
  1. Create your account in TravisCI & Code Coverage
  2. Configure TravisCI environment variables DANGER_GITHUB_API_TOKEN, GH_TOKEN & NPM_TOKEN with right permissions (you can find in their websites) for repo access to release new versions & intercept in pull requests
  3. Make sure you have these options checked in TravisCI:

React Typescript Component Development Kit

  1. Follow contributing
  2. in your project, run the following:
yarn add https://github.com/yourusername/react-ts-cdk
  1. import your components developed in this repo & use them!

Features

  • [x] React
  • [x] Typescript
  • [x] Storybook
  • [x] Jest
  • [x] Enzyme
  • [x] Webpack
  • [x] Prettier
  • [x] Commitizen

Workflow

See presentation

Repository Workflow

Contributing

  1. Fork it!
  2. install dependencies: yarn install
  3. Maybe use storybook to test your component in its final UI version: yarn run storybook
  4. If using storybook, then open localhost:6006 to get a hot module replacement environment to visualize your component after every file saved
  5. Create your feature branch: git checkout -b my-new-feature
  6. Check our workflow (it will help you understand how you should develop your feature), if you haven't yet.
  7. Commit your changes: yarn run commit
  8. Push to the branch: git push origin my-new-feature
  9. Submit a pull request :smile:

License

MIT