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

fs-react-component

v0.0.2

Published

This is a sample fable component which could be published as a stand alone React component.

Downloads

3

Readme

Fable React Component

This is a sample fable component which could be published as a stand alone React component.

Requirements

Building and running the app

  • Install JS dependencies: yarn
  • Start Webpack dev server: yarn start or yarn build
  • Make the package visible on your local system using yarn link
yarn link v1.13.0
success Registered "fs-react-component".
info You can now run `yarn link "fs-react-component"` in the projects where you want to use this package and it will be used instead.
Done in 0.09s.

Meanwhile...

  • Create a new plain js/react project
  • For this example I'll use create-react-app to save some setup.
npx create-react-app my-app
cd my-app
yarn link "fs-react-component"
yarn start
  • Now the fs-react-component is linked to my-app by node_modules
  • Open App.js and add this import
import { StandardComponent, FunComponent, Fable5FunComponent } from 'fs-react-component'
  • Then use the component like any other react component
    <StandardComponent name="standard" />
    <FunComponent name="bare" />
    <Fable5FunComponent name="Memo Component" />
  • If you ran yarn start in both fs-react-component and my-app you should be able to make changes to index.fs and see them reflected in my-app automatically.
  • See comments in the source about why you might prefer one component type over another.
  • That's it 🎉

Publishing

  • Remember to change the package name in package.json
  • yarn login with your npmjs.com credentials
  • yarn publish
  • Tell your friends