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

@flatfile/turntable

v2.2.1

Published

> Simple, extendable data table focused on performance

Downloads

3

Readme

Turntable

Simple, extendable data table focused on performance

Installation

Turntable can be installed with npm

npm install @flatfile/turntable

or yarn

yarn add @flatfile/turntable

Usage

const columns = [
  { value: 'Name' },
  { value: 'Phone' },
  { value: 'City' },
  { value: 'State' },
]

const rows = [
  {
    cells: [
      { value: 'Julianne Littel' },
      { value: '189-242-5961' },
      { value: 'South Sventown' },
      { value: 'Idaho' },
    ],
    position: 0,
    rowIndex: 1,
  },
  {
    cells: [
      { value: 'Adela Skiles' },
      { value: '582-187-2342' },
      { value: 'East Keegan' },
      { value: 'Delaware' },
    ],
    position: 1,
    rowIndex: 2,
  },
  {
    cells: [
      { value: 'Naomie Dach' },
      { value: '766-231-5964' },
      { value: 'Port Mackville' },
      { value: 'Missouri' },
    ],
    position: 2,
    rowIndex: 3,
  },
  {
    cells: [
      { value: 'Dr. Corine Hirthe' },
      { value: '327-913-2735' },
      { value: 'Lake Freder' },
      { value: 'Alabama' },
    ],
    position: 3,
    rowIndex: 4,
  },
]

;<Table
  columnConfig={columns}
  count={4}
  initData={rows}
  visibleRows={4}
  rowHeight={40}
/>

Developing locally

The app development environment can be started via one of two ways: NPM or Docker. Docker offers the additional ability to test package distributions locally.

Using NPM

Starting the app locally: npm run start

Watch types: npm run type-check:watch

Testing the app: npm run test

Starting Storybook: npm run storybook

Building: npm run build

Using Docker

Starting the app: docker-compose up dev

Testing the app: docker-compose run --rm dev npm run test

Watch types: docker-compose run --rm dev npm run type-check:watch

Starting Storybook: docker-compose up storybook

Test package in sandbox: docker-compose up pack

Versioning & Publishing Packages

Warning

Do NOT publish packages manually from your local environment. This will confuse the automation and make sadness.

Package publishing is automated through changeset and github workflows. To instigate publication:

  1. Make a change to a package
  2. Run npm run changeset, choose the package(s) that were modified, and follow instructions to fill out changelog details
  3. Push the resulting .changeset file along with the package changes from the first step
  4. Create PR with these changes and merge into main

This will trigger a github action to create a new PR with the increased version and changelog. Once this PR gets merged, CI runs again and releases the package(s) to npm.