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

@freska/freska-ui

v2.9.11

Published

React component library designed to help developers create unified Freska experience across different frontends.

Downloads

29

Readme

Freska UI Components

React component library designed to help developers create unified Freska experience across different frontends.

Using the React components

TODO

Style guide

Run the following command to start style guide dev server:

npm run styleguide

Run the following command to build a static version of style guide:

npm run styleguide:build

Publishing New Version to NPM

Before updates in master can be used in external projects, a new NPM version has been published. To do so, follow these steps:

Don't have (or don't know if you have) versioning and publishing rights? Let somebody know.

  1. First, build the styleguide to include the latest updates.

Before updates in master can be used in external projects, a new NPM version has to be published. To do so, follow these steps:

npm run build
  1. Then increment the NPM version by using:
  • major is for large X.0.0 changes
  • minor is for smaller but substantial updates such as entirely new components
  • patch is probably the most common used for small updates to existing components
npm version major|minor|patch
  1. Push the latest build to Github
git push
  1. Finally, publish the latest version to NPM
npm publish