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

@wellcome/corporate-components

v0.0.0

Published

Component library for main Wellcome Trust corporate site

Downloads

4

Readme

Corporate Components

Table of contents

Usage

1. Clone this repo

(TODO: setup npm package location)

git clone [email protected]:wellcometrust/corporate-components.git

2. Setup NPM Link (for local development)

You need to setup a symlink inside the corporate-components project, in order to use it inside another local project. From the corporate-components root, run:

npm link

npm link commands will need to be rerun after any npm install operation.

Read more about npm link

3. Setup a consumer project

If you need to set up a new project, we recommend using create-react-app to get started quickly.

Once you have a project you want to import corporate-components into, cd in to your new project's root and run:

npm link @wellcome/corporate-components

Please note that corporate-components must first be compiled or built in order to use the compiled distributable files.

4. Import desired component(s) into your project

import { ComponentName } from '@wellcome/corporate-components';

5. Import styles

import '@wellcome/corporate-components/dist/styles.css';

Issues

React Hooks errors?

This issue is caused by the very nature of the symlinks which npm uses to create the links. Effectively React is flagging up a possible duplicate instance of React.

To get round this you will need to link to the app instance of React by running the following command from the library root (assuming the library and app are in the same folder).

npm link ../corporate-react/node_modules/react

Permissions (with npm link)

sudo npm link

Development

Develop

Watch and compile files on change.

npm run dev

Build

Builds files for distribution.

npm run build

Run Storybook

Storybook is a UI development environment we are using to power our component library. Using Storybook allows us to work on components in isolation.

npm run storybook