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

@tablecheck/scripts

v2.3.10

Published

Configuration and scripts forked from Create React App.

Downloads

58

Readme

Scripts Package

Usage of this package is normally: tablecheck-scripts <script name>. See sub-packages for script details.

Setup Requirements

For these scripts to work the following structure should be adhered to. It is recommended that you run npx @tablecheck/scripts init to get the correct structure of your project.

- project
- | - src (react and javascript files go here)
- | - public (static files like index.html and favicons should go here
- | - config (usage of node-config and special scripts - see `config/config.js`)
- | - | - default.json

Config setup

We use a combination of node-config and preprocesser based values. This config is exposed via a global CONFIG variable, the types are automaticaly inferred from the config/default.json file when any of the following scripts are run; tsc lint init precommit build.

Settings

Additional settings can be provided inside of your package.json file or inside a rc file as described by cosmiconfig ([email protected] for example). All paths are relative to the root of your project. This file can be overwritten by providing the --scriptConfig=<filepath> option, but usually shouldn't be necessary.

{
  "@tablecheck": {
    "setupTests": "./root/relative/path/to/test/setup/file.js",
    "testRoots": ["packages/Button/src/tests", "packages/Layer/src"]
  }
}
  • setupTests: This file is how you can load a custom version of setupTests.js for Jest, by default we have enzyme, react-16 and emotion snapshot testing configured.

  • testRoots: (Not Recommended) Usually this won't be needed as the test script will automatically detect src folder test files. This is relevant for monorepo's like this one where running lerna run test gives a rather slow and garbled output. Using this array of relative folder paths you can tell jest where to look for tests under.

  • Currently Supported and used Polyfills are:

    • https://www.promisejs.org/ Promise polyfill, supports .finally
    • object-assign supporting Object.assign

    Unlike create-react-app we do not polyfill the usage of whatwg-fetch as in our setup we use axios.