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

wvs-org-shared-components

v1.3.0

Published

A shared component package for use by WVS

Downloads

156

Readme

WVS Org Shared Components

This is a shared component library for use by WVS org. We have made this accessible under MIT license. Please see the License for full details.

Installation

Using npm: npm install wvs-org-shared-components

Usage

Import the component you require:

import React from 'react';
import { Button } from 'wvs-org-shared-components';

function App() {
  return (
    <Button
      disabled={someDisabledState}
      isUpdating={someInUpdatingState}
      onClick={() => console.log('I have been clicked!')}
      small={true}
      updatingText={'Component is updating...'}
      variant={'secondary'}
    >
      Click me!
    </Button>
  );
}

export default App;

Adding to the library

In order to add into the library:

  • Take a copy of an existing component in the /src/components directory
  • Rename and update the component directory, component.tsx, index.ts and styles.tsx
  • Ensure that the new component is included in src/components/index.ts

Once updates are made and you are ready to deploy:

  • Update package.json to increase the version number
  • Have a PR made and merged to main branch
  • Run npm run rollup
  • Run npm publish
  • Run git tag -a vx.x.x -m "Release vx.x.x"
  • Run git push --tags
  • Go here in browser and click "Draft a new release"
  • Select the tag you just pushed
  • Add a release title that matches the version number
  • Complete an explanation of the release, some things to note on this:
    • Add ##What's Changed at top
    • Add ### New Features and include a list below
    • Prepend any items with [Breaking/Deprecation/Feature/Improvement] making sure to order them as shown here
  • Make sure that "Set as the latest release" is selected and press "Publish Release"

Components that are being phased out

The following components are being phased out and should not be used in new projects:

  • CallToAction
  • Content
  • Dialog
  • Hero
  • HeroAspectRatio
  • IframeWrapper
  • Image
  • ImageWrapper

They will continue to be supported in existing projects but will not be updated with new features or bug fixes.