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

oijoij

v1.0.116

Published

This project contains all the pages needed for browsing entities and searching them. The aim is to replace the CluedIn.Webapp project with this one when all the pages ( including the Admin page ) will be ported to REACT.

Downloads

8

Readme

#CluedIn Widget

This project contains all the pages needed for browsing entities and searching them. The aim is to replace the CluedIn.Webapp project with this one when all the pages ( including the Admin page ) will be ported to REACT.

The project is divided in 2 parts. The first one is the main REACT application and the second all all the widgets to build an Entity Page.

All the widgets are located in the folder 'widget' in the project root.

##Pre-requesite

You need a version of node and npm installed.

Some basic knowledge of React is required.

The main plugins used are: react, react-router, redux, react-intl,...

The project is written in ES6 using Babel and Webpack to generate the APP.

##Getting Started

Install dependencies

npm install

Generate the app ( and/or the style )

gulp

Run the Web Dev Server ( react hot reloading )

npm run dev

##Project Structure

###core

Contain the react application.

###src

Contain some scripts needed by the NODE.JS Server ( located in CluedIn.Webapp ) to serve the appropriate static files to the APP or any page ( self-injectable widget ).

###iso

All stateless methods which can be used in the browser or in a node environment. If you have a stateless method which looks generic enough, please, add them in the ISO folder.

PS: 'iso' stands for 'isomorphic'.

###locales

Contain all the translation for the application used by a plugin called React-intl.

##Styling the application

###Generic Styling

This project is using SCSS.

The styles are located in the /core/style.

###Styling a React component

This project uses React-Css-Module for styling component. This enables us to have self-contained CSS.

Please, refer to https://github.com/gajus/react-css-modules for more information.

##Redux

This project uses Redux for structuring the application.

##Create a specific Entity Page

The routing of the app is dynamically generated based on the entity configuration (/core/config/entity.js).

If the entity config object has the parameter 'url' present, the app will create a router for it

If the entity config object does not have the 'url' parameter, the app will use the defaultEntity page

##Best-practises

  • Keep React component as generic as possible ( avoid using the Connect method from the Redux library ).
  • Do not hesitate to create React components
  • Favor props over state in your React component. State is generally used by wrapper components
  • Dispatch your (redux) actions in wrapper components
  • Try to keep the style self-contained and favor SCSS mixins and placeholders inside your component scss file
  • If you have small images, leverage Webpack to load them in base64 directly in the application