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

@inthepocket/create-itp-react-app

v0.1.2

Published

[![version][version-badge]][package] [![MIT License][license-badge]][license]

Downloads

18

Readme

create-itp-react-app

version MIT License

Generates an ITP-ready React App.

Uses create-react-app under the hood. Adds some extra features and example files within our common directory structure.

Typescript is enabled by default.

Getting started

$ npx @inthepocket/create-itp-react-app <your-project-name>
$ cd <your-project-name>
$ npm start

Features

1 should be replaced by eslint in the near future, as pointed out by @thibmaek

2 postcss & postcss-preset-env now come with react-scripts (stage 3 configured). Unfortunately we still need to rewire, because we'll need stage 1 & the custom-media-queries feature.

Generated project structure

├── design-docs
└── src
    ├── __mockdata__
    ├── app
    │   └── screens
    ├── common (import from generated-project-name/common)
    │   ├── assets
        |   ├── fnt
        |   ├── img
    │   ├── components
    │   │   ├── atoms
    │   │   ├── molecules
    │   │   └── organisms
    │   └── primitives
    └── core (import from generated-project-name/core)
        ├── actions
        ├── reducers
        ├── sagas
        ├── schemas
        ├── selectors
        └── services
        └── types

Local packages

  • generated-project-name/common
  • generated-project-name/core
  • generated-project-name/mock

Example files

The generated project comes with some example files that demonstrate:

Development (running the generator locally)

  • run the prepublishOnly script before running the generator (to generate the design-docs template folder)
  • run node index.js <MY_PROJECT_NAME>
  • a generated project is created in the folder <MY_PROJECT_NAME>

Known issues

Error: ENFILE: file table overflow

Stack trace

$ (node:56347) UnhandledPromiseRejectionWarning: Error: ENFILE: file table overflow, open '<LOCAL_PATH>/node_modules/jest-matchers/build/spyMatchers.js'
$ (node:56347) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise whichwas not handled with .catch(). (rejection id: 1)
$ (node:56347) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Workaround

$ echo kern.maxfiles=65536 | sudo tee -a /etc/sysctl.conf
$ echo kern.maxfilesperproc=65536 | sudo tee -a /etc/sysctl.conf
$ sudo sysctl -w kern.maxfiles=65536
$ sudo sysctl -w kern.maxfilesperproc=65536
$ ulimit -n 65536

Jira ref: DESSSYS-26