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

@fixt/components

v1.1.69

Published

![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)

Downloads

72

Readme

Fixt Component Library

GitHub license npm version Codeship Status for fixt/component-library

Welcome to the Fixt Component Library. A shared repository of React components.

Usage

  1. Install
  npm install @fixt/components
  npm install styled-components --save
  1. Include these stylesheets in your html file
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css">
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:300,400,500">
  1. Wrap your root component with the styled-components ThemeProvider
import React from 'react';
import { ThemeProvider } from 'styled-components'
import { themes } from '@fixt/components';

import App from './index'

const Root = () => (
<ThemeProvider theme={themes.standard}>
  <App />
</ThemeProvider>);
  1. Using the React components
import React from ‘react’;
import { Button } from '@fixt/components';

const BoringButton = () => (
  <Button />
);

Storybook Development

  1. Install & Build dependencies
  npm run build
  1. Start the Storybook server
  npm run storybook:dev
  1. Runs storybook at http://localhost:6006

Storybook Deployment to Github Pages

  npm run storybook:deploy

Publish New Versions

  npm run publish

Updating Versions

Make version changes to package.json:

  1. Create a branch of component-library. Open the package.json file and locate the package to be modified. Change the version number to the new version number.
  "material-table": {
      "version": "1.64.0", 
  1. Go to the top of the file and find the version number of the component-library. Bump the version up by 1 point (1.1.8 will be changed to 1.1.9).
    {
  "name": "@fixt/components",
  "version": "1.1.13",
  1. After modifying the file, be sure to update the .lock file with
yarn install
  1. Push changes of branch (git add, git commit, git push) and submit a pull request to be merged into master.

Publish changes to @fixt/components using npm:

  1. If you are not already logged into npm, in the terminal command line
    npm login

This will bring up a prompt for Username: and Password:

  1. Change into the component-library master directory (make sure it is not the branch) and type in the command
  npm publish
  1. This should start the process of publishing the new version. Check at https://www.npmjs.com/settings/fixt/packages to make sure the new version is published.

Update the version number in HQ:

  1. Create a branch of HQ. Go to the client directory and in the package.json file locate @fixt/components. Change the version to match the new published version.
    "@fixt/components": "^1.1.8",
  1. After modifying the file, be sure to update the .lock file with
    yarn install
  1. Push the changes and submit a pull request to merge into HQ.