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

generate-connect-types

v0.2.10

Published

[![npm version](https://badge.fury.io/js/generate-connect-types.svg)](https://badge.fury.io/js/generate-connect-types)

Downloads

51

Readme

generate-connect-types

npm version

What is this?

This is something that is supposed to generate interfaces for your connected components

Given a input like

import {connect} from 'react-redux'
import {State} from './somewhere-appstate'

const t = connect(
  (state: State) => ({
    index: state.index,
    name: state.name,
    ble: state.bla,
  }),
  () => ({
    dispatch: () => console.log('hej'),
  }),
)(Comp)

it outputs

interface ConnectProps {
  index: number
  name: string
  ble: Bla
  dispatch: () => void
}

This package uses typescript to create a program from the file sent as the argument and tries to extract information from the connect() call to build an interface for given props.
It also uses prettier to format the interface before inserting it into the file.

Why?

Because I'm lazy and writing types for connected props is boring.

Try it out

The best way to try this is to use npx or install the module globally.

# Be sure to make the path relative from the folder you re in
# If useing npx
npx generate-connect-types src/components/foo.tsx

# Or install it globally
npm i -g generate-connect-types
generate-connect-types src/components/your-awesome-component.tsx

Now src/components/foo.tsx should have an autogenerated interface for the connected props

Build

# Install deps
yarn # or npm i

# Build code
yarn compile # compiles code to javascript

yarn compile:watch # compiles with watch mode

Test

yarn test

# or watch mode
yarn test:watch

Developing

If you want to contribute or tinker with this, this is how my workflow looks like:

  1. Set the compiler in watch mode by running yarn compile:watch
  2. In another terminal window, run node index.js path/to/component.tsx (there are components in tests/assets/ that you can use)
  3. Hack away!

The components in tests/assets gets a lot of interfaces so you should probably remove them. Running the tests will reset them tho. Or you could revert the file in git.

Todo

  • [x] write the interface to the same file
  • [x] integrationtests
  • [x] windows support
  • [ ] unit tests
  • [x] make it work for deeply nested literal object types
  • [x] figure out a way to get more info about an object type instead of just returning it as string
  • [ ] make a vs code extension out of it
  • [ ] configuration (interface name, prettier options)