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

@privy-eng/privy-components

v1.0.6

Published

Component library for Privy

Downloads

2

Readme

Privy Component Library:

Setup steps:

  1. SETUP YOUR MACHINE:
    • Make sure you have yarn installed in your machine.
      • Follow this link to install yarn: https://linuxize.com/post/how-to-install-yarn-on-ubuntu-18-04/
    • Install NVM to manage the versions of node.
      • Follow this link to install NVM: https://www.liquidweb.com/kb/how-to-install-nvm-node-version-manager-for-node-js-on-ubuntu-12-04-lts/
    • Clone the repo to your local machine. git clone {ssh/https}
    • Select the right the version of yarn for privy-components by specifying it to nvm:
      1. Check the node version. node --version
      2. Change nvm to use the node version nvm run {node_version}
  2. SETUP PRIVY-COMPONENT REPO:
    • In order to run Storybook you will have to run yarn start.
    • You may get an error that says you need to add the private NPM_TOKEN, either login to npm with privy's engineering account saved in last pass, or create an account and let the admin invite you to the project.
    • Once you have the NPM_TOKEN follow these steps: https://docs.npmjs.com/using-private-packages-in-a-ci-cd-workflow.
    • Don't forget to exit and reopen the terminal.
    • Run yarn start and it should work!

    CLI commands:

  • To generate a new component boilerplate run yarn gernerate:component component-name.
    • The name of the component should always be lower-dashcase (e.g loading-component as opposed to LoadingComponent). The generator will automatically turn component-name into const ComponentName = (props) {..}
    • The generator automatically creates a webpack.config.js with proper entry and output paths.
    • Adds @babel/preset-react @babel/core webpack webpack-cli to package.json and runs yarn install
    • The generator creates a packages/component-name/lib/ComponentName.stories.js file for use with storybook.
    • The generator creates a functional react component boilerplate code in packages/component-name/lib/ComponentName.js - this is where you will build your component.

TODO:

  • fill in Lerna commands.

Create new package

Publishing

To publish a new package, or an update that was made to an existing package you will need to do the following:

  • cd into the package you want to publish
  • run yarn publish
  • When prompted, enter a new patch/minor/major version increment that matches the update being made (modelled after semver)
  • If publishing a beta feature just for testing, it is recommended to use the --canary flag