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

encirclelabs

v0.8.4

Published

UI library

Downloads

19

Readme

Welcome to Cybertron - EncircleLabs inner UI library 👋

Quick start

To get it worked with published npm library:

  • Add to aliases.js the next rows:
const getLibrary = () => process.env.REACT_APP_LIBRARY_PATH || 'encirclelabs';

module.exports = {
...
  • To overwrite the default order in which webpack will look for your dependencies and make your parent application node_modules more prioritized than component node module resolution order (the same should be used for all packages that are used in both projects):

react: resolveApp('node_modules/react'), 'react-router-dom': resolveApp('node_modules/react-router-dom'), '@material-ui/styles': resolveApp('node_modules/@material-ui/styles'), '@material-ui/core': resolveApp('node_modules/@material-ui/core'),

  • Add path to component library (for local development it'll be path from env.local to local library, for deployed version of parent app it'll be published npm library):

'@library': getLibrary(),

}

  • config-override.js should include removeModuleScopePlugin option and looks like that
const { addWebpackAlias, override, removeModuleScopePlugin } = require('customize-cra');
const aliases = require('./aliases');

module.exports = override(removeModuleScopePlugin(), addWebpackAlias(aliases));

To work with locally run instance:

  1. In the project directory, you can run yarn

  2. Run yarn watch

  3. Add to env.local file your own local path to dist folder of cybertron library REACT_APP_LIBRARY_PATH =/Users/yourUsername/yourPathToFolder/cybertron/dist

  4. To publish changes to npm it's enough just to merge changes to main, they will be published automatically