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 🙏

© 2025 – Pkg Stats / Ryan Hefner

carpentr

v1.0.6

Published

Data Tables made easy

Readme

Carpentr

Can't find an easy way to organize your table data without sacrificing all the design? Neither could we. Introducing Carpentr, a react hook inspired library that empowers you to handle the look and feel while we take care of the rest. Carpentr is small, performant, and fits nicely into any size react project.

Docs

The Install

You can install Carpentr with either NPM or Yarn

NPM

$ npm install --save carpentr

Yarn

$ yarn add carpentr

The Basics

import React, { useEffect } from 'react'
import PropTypes from 'prop-types'
import { useCarpentr } from 'carpentr'

const Users = () => {
const data = [
  { firstName: 'Ferris', lastName: 'Bueller', dob: '3-21-1962', occupation: 'student' },
  { firstName: 'Cameron', lastName: 'Frye', dob: '7-1-1956', occupation: 'student' },
  { firstName: 'Sloane', lastName: 'Peterson', dob: '6-19-1967', occupation: 'student' }
]

  const payload = useCarpentr({
    initialData: data,
    sortColumn: 'firstName',
    searchKeys: ['firstName', 'lastName']
  })

  render() {
    const renderTable = () => {
      return (
        <div>
          <div className='form-row mb-3'>
            <input
              className='form-control'
              placeholder='Search...'
              value={payload.search}
              onChange={payload.setSearchTerm}/>
          </div>
          <table className='table table-hover mb-4'>
            <thead className='bg-primary text-white'>
              <tr>
                <th name='firstName' onClick={payload.setColumnSortToggle}>FirstName</th>
                <th name='lastName' onClick={payload.setColumnSortToggle}>LastName</th>
                <th name='dob' onClick={payload.setColumnSortToggle}>Date Of Birth</th>
                <th name='occupation' onClick={payload.setColumnSortToggle}>Occupation</th>
              </tr>
            </thead>
            <tbody>
              {payload.visibleData.map((user, i) => {
                return (
                  <tr key={i}>
                    <td>{user.firstName}</td>
                    <td>{user.lastName}</td>
                    <td>{user.dob}</td>
                    <td>{user.occupation}</td>
                  </tr>
                )
              })}
            </tbody>
          </table>

          <div className='row my-4 justify-content-between'>
            <div className='col-md-6'>
              <div className='form-inline'>
                <label className='my-1 mr-2'>Result set: </label>
                <select
                  className='form-control'
                  value={payload.resultSet}
                  onChange={(e) => { payload.setResultSet(parseInt(e.target.value)) }}>
                  <option>5</option>
                  <option>10</option>
                  <option>15</option>
                </select>
              </div>
            </div>

            <div className='col-md-6'>
              <ul className='pagination rounded-flat pagination-primary d-flex justify-content-center'>
                <li
                  className={payload.prevDisabled ? 'page-item invisible' : 'page-item'}
                  onClick={() => { payload.setCurrentPage(payload.currentPage - 1) }}>
                  <a className='page-link' aria-label='Next'>
                    <span aria-hidden='true'>&laquo;</span>
                    <span className='sr-only'>Previous</span>
                  </a>
                </li>

                {payload.paginationButtons.map((page, i) => {
                  return (
                    <li key={i} className={payload.currentPage === page ? 'page-item active' : 'page-item'}>
                      <span className='page-link pointer' onClick={() => { payload.setCurrentPage(page) }}>{page}</span>
                    </li>
                  )
                })}

                <li
                  className={payload.nextDisabled ? 'page-item invisible' : 'page-item'}
                  onClick={() => { payload.setCurrentPage(payload.currentPage + 1) }}>
                  <a className='page-link' aria-label='Next'>
                    <span aria-hidden='true'>&raquo;</span>
                    <span className='sr-only'>Next</span>
                  </a>
                </li>
              </ul>
            </div>
          </div>
        </div>
      )
    }

    return (
      <div className='container mt-5'>
        <div className='row'>
          <div className='col-md-12'>
            <h1>Users</h1>
            {renderTable()}
          </div>
        </div>
      </div>
    )
  }
}

export default Users

The Options

|Prop |Type |Example |Default | Required | |--- |--- |--- |--- |--- | |initialData |Array |[{...},{...},{...}] | |true | |search |String |'firstName' | | | |searchKeys |Array |['firstName'] |all keys | | |sortColumn |String |'lastName' | | | |sortOrder |String |'desc' |'asc' | | |currentPage |Number |2 |1 | | |resultSet |Number |20 |10 | | |pageNeighbors |Number |3 |2 | |

initialData

This is the array of data you wish to put into a table format. If your data is coming back from an API call, then pass along that data however you see fit. Carpentr checks for updates as its given new data and only re-renders when it detects new information.

  const data = [...users] 

  const payload = useCarpentr({ initialData: data })

searchKeys

You will be given a method in the next section called setSearchTerm that will allow you to do a filtered search on the objects retured to you. By default your search term will be applied to every single key: value pair found in each object in your initialData. searchKeys is a way to specify which keys you want the searchTerm to be applied against. In the example below our search will only be looking for matches with the firstName and lastName and NOT dob or occupation. It is highly recommended to pass along a value for searchKeys to improve the performance of this filter feature.

  const data = [...users]

  const payload = useCarpentr({
    initialData: data,
    searchKeys: ['firstName', 'lastName']
  })

sortColumn

If you know in advance what column you wish to sort on then you can pass that information along here. Just tell Carpentr what key in each object inside your array of initialData you wish to sort on.

  const data = [...users]

  const payload = useCarpentr({
    initialData: data,
    searchKeys: ['firstName', 'lastName'],
    sortColumn: 'lastName'
  })

sortOrder

By default Carpentr will sort your data in asc (ascending order). If you wish for it to sort in descending order you are given the ability to do that here.

  const data = [...users]

  const payload = useCarpentr({
    initialData: data,
    searchKeys: ['firstName', 'lastName'],
    sortColumn: 'lastName',
    sortOrder: 'desc'
  })

currentPage

If for some reason you don't want the table to start on the first page of results you can specify the starting page here. This is helpful for those of you who store your page number as a param in your route.

  const data = [...users]
  const { currentPage } = useParams()

  const payload = useCarpentr({
    initialData: data,
    searchKeys: ['firstName', 'lastName'],
    sortColumn: 'lastName',
    sortOrder: 'desc',
    currentPage: currentPage
  })

pageNeighbors

Carpentr will provide to you the pagination logic for your tables. Here is your opportunity to specify how many pages you wish to show up in that pagination array. Some examples:

  const data = [...users]

  const payload = useCarpentr({
    initialData: data,
    pageNeighbors: 1 // will give you: [1, 2, 3]
  })

  const payload = useCarpentr({
    initialData: data,
    pageNeighbors: 2 // will give you: [1, 2, 3, 4, 5]
  })

  const payload = useCarpentr({
    initialData: data,
    pageNeighbors: 3 // will give you: [1, 2, 3, 4, 5, 6, 7]
  })

resultSet

By default Carpentr will return the first 10 results to you to display on the screen. If you would like to change the default setting just pass your desired return into resultSet.

  const data = [...users]

  const payload = useCarpentr({
    initialData: data,
    resultSet: 20
  })

The Payload

By running useCarpentr({...options}) you are returned a Payload with all of the values and helper methods you need to manage your Table.

|Props |Type | |--- |--- | |currentPage |Number | |nextDisabled |Boolean | |prevDisabled |Boolean | |paginationButtons |Array | |setCurrentPage |Function | |resultSet |Number | |setResultSet |Function | |search |String | |setSearchTerm |Function | |setColumnSortToggle |Function | |sortColumn |String | |sortOrder |String | |totalPages |Number | |visibleData |Array |

currentPage

currentPage is the active (or current) page number that the user is on. Great for applying the active class in pagination

{payload.paginationButtons.map((page, i) => {
  return (
    <li key={i} className={payload.currentPage === page ? 'page-item active' : 'page-item'}>
      <span className='page-link pointer' onClick={() => { payload.setCurrentPage(page) }}>{page}</span>
    </li>
  )
})}

nextDisabled / prevDisabled

In pagination its common to have a next / previous buttons. nextDisabled and prevDisabled lets you know if your next or previous buttons ought to be disabled or made invisible as you'll see in my example below.

<ul className='pagination rounded-flat pagination-primary d-flex justify-content-center'>
  <li
    className={payload.prevDisabled ? 'page-item invisible' : 'page-item'}
    onClick={() => { payload.setCurrentPage(payload.currentPage - 1) }}>
    <a className='page-link' aria-label='Next'>
      <span aria-hidden='true'>&laquo;</span>
      <span className='sr-only'>Previous</span>
    </a>
  </li>

  {payload.paginationButtons.map((page, i) => {
    return (
      <li key={i} className={payload.currentPage === page ? 'page-item active' : 'page-item'}>
        <span className='page-link pointer' onClick={() => { payload.setCurrentPage(page) }}>{page}</span>
      </li>
    )
  })}

  <li
    className={payload.nextDisabled ? 'page-item invisible' : 'page-item'}
    onClick={() => { payload.setCurrentPage(payload.currentPage + 1) }}>
    <a className='page-link' aria-label='Next'>
      <span aria-hidden='true'>&raquo;</span>
      <span className='sr-only'>Next</span>
    </a>
  </li>
</ul>

paginationButtons

paginationButtons is an array of the page numbers you need to display in your pagination. A few examples above show how we .map() over this array to create our pagination.

setCurrentPage

This method allows you to set a new currentPage within your pagination. Examples of this method can be found above.

resultSet

resultSet is how many items will be returned in our visibleData array. The default value is 10 however when creating your instance of Carpentr() you can pass in a new default. If you want to let your user specify the result set then please use the setResultSet method

setResultSet

Sometimes you want to give your user the flexibility of setting how many results they wish to see in a given table. This method allows you to give them the ability to do just that.

<div className='form-inline'>
  <label className='my-1 mr-2'>Result set: </label>
  <select
    className='form-control'
    value={payload.resultSet}
    onChange={(e) => { payload.setResultSet(parseInt(e.target.value)) }}>
    <option>5</option>
    <option>10</option>
    <option>15</option>
  </select>
</div>

search / setSearchTerm

these two go hand in hand as setSearchTerm will be the method you use to set the value for search. Both of these values will be passed back in payload and can be used like this in your renderTable method:

<div className='form-row mb-3'>
  <input
    className='form-control'
    placeholder='Search...'
    value={payload.search}
    onChange={payload.setSearchTerm}/>
</div>

setColumnSortToggle

Sorting a table by its columns is a common action a user expects to take. This method requires you set a name attribute on the <th /> tag that is equal to the key that that column is displaying. This method toggles between 'asc' and 'desc' orders.

<thead className='bg-primary text-white'>
  <tr>
    <th name='firstName' onClick={payload.setColumnSortToggle}>FirstName</th>
    <th name='lastName' onClick={payload.setColumnSortToggle}>LastName</th>
    <th name='dob' onClick={payload.setColumnSortToggle}>Date Of Birth</th>
    <th name='occupation' onClick={payload.setColumnSortToggle}>Occupation</th>
  </tr>
</thead>

sortColumn

If you wish to show your user which column is being sorted this value is being passed back to you so you can manage your css accordingly

sortOrder

If you wish to show your user in which direction the column is being sorted this value is being passed back to you so you can manage your css accordingly

totalPages

totalPages is a derived value from initialData / resultSet. If you wish to tell your user how many pages they potentially need to paginate through then this is your value.

visibleData

visibleData is the data you will want to render onto the screen. This data has gone through all of the sorting and filtering.

<tbody>
  {payload.visibleData.map((user, i) => {
    return (
      <tr key={i}>
        <td>{user.firstName}</td>
        <td>{user.lastName}</td>
        <td>{user.dob}</td>
        <td>{user.occupation}</td>
      </tr>
    )
  })}
</tbody>