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 🙏

© 2026 – Pkg Stats / Ryan Hefner

internal-apps-react-components

v1.0.0

Published

Collection of shared React components for internal apps

Readme

Internal Apps React Components

Collection of shared React components for internal apps

noc-app-menu

Applications menu for internal apps

Sidebar menu

noc-installed-devices-label

Installed devices label with tooltip

Label with tooltip

Development

Creating a new component

Duplicate the boilerplate folder.

Update the package.json and README.md with your new component details.

Install NPM development dependencies for this new component:

cd your-component-folder
npm i

Start Webpack to build the component and watch files changes:

npm run watch

Build the component:

npm run build

The build will be created inside the dist folder in your component root directory.

Publish to NPM (make sure the package.json has been updated with your component name before publishing):

npm publish

Assets

The boilerplate supports:

  • Javascript
  • Typescript
  • CSS files
  • PNG files
  • SVG fonts

If your component uses unsupported file types, please update the webpack.config.js to add an appropriate loader and/or the src/custom.d.ts to allow support of different file types.

Dependencies

By default, the boilerplate relies on React & Ant. Those dependencies MUST NOT be included in the dependencies section of the package.json. Instead, they have to be listed under peerDependencies. By doing this, NPM will uses the dependency package (eg. React) from the host project instead of duplicating it in your component node_modules folder.

Troubleshooting

Error: Invalid hook call. Hooks can only be called inside of the body of a function component

Make sure you did not include React in the dependencies of your component. Also, when testing a component, you should link the React module from your host project inside the component folder:

npm link ~/your-other-project/node_modules/react

https://reactjs.org/warnings/invalid-hook-call-warning.html

Error: Failed to minify the code from this file

If this error occurs when using the new component in an host project, it is possible that the component uses newer Javascript features not supported by the current version of the host project: https://create-react-app.dev/docs/troubleshooting/#npm-run-build-fails-to-minify

ERROR in [PACKAGE_FILE] Module parse failed: Unexpected token (LINE) You may need an appropriate loader to handle this file type

Make sure that the compiler target option from the component is also supported by the compiler lib option of the host project (tsconfig.json/jsconfig.json).