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

@t4y3/fig

v0.3.6

Published

Fig - library for gallery of Riot tag

Downloads

57

Readme

Fig

MIT License Version

Fig - library for gallery of Riot tag
You can check each component like a React Styleguidist by list.
It is also possible to check only specific component information.
https://www.npmjs.com/package/@t4y3/fig

Demo

  • https://fig-example.netlify.com/

Capture

Index Page

index

Other pages

Component|Types of Component|Full :--:|:--:|:--: components|components type|full

Description

Mount the custom tag specified in tags in the iframe.
It is for displaying and confirming the custom tag created.
Use it like a style guide.

Install

npm i @t4y3/fig

Usage

In local environment

# Server start
fig-start

Access localhost: 8080

Hosting a style guide

  • Please build and generate a static file
# Generate static file
fig-build
# or Specify the dist directory(default: dist)
fig-build docs

Configuration

.fig/config.js
.fig/head.html
path/to/fig.js

.fig/config.js

Set the following rule in .fig/config.js.

module.exports = {
  'title': 'Your project name',
  'bundle': 'dist/bundle.js',
  'figures': [
    'path/to/components1/fig.js',
    'path/to/components2/fig.js',
    'path/to/components3/fig.js'
  ]
};

  • title - Title of the Styleguide
    • default: Fig
  • bundle - files required to display custom tags

.fig/head.html

<link rel="stylesheet" href="path/to/style.css">
<script type="text/javascript" src="path/to/script.js"></script>
  • Add resources other than bundle files.
  • It will be added in the head tag.

fig.js.

const InFig = require('@t4y3/fig');

InFig.set('Button')
  .add('red', () => {
      return `<my-button type="{ type }" text="click"></my-button>`
    }, {
      type: 'red'
    })
  .add('blue', () => {
      return `<my-button type="{ type }" text="click"></my-button>`
    }, {
      type: 'blue'
    });

Development

Installing

# Install npm packages
npm i

Running

# build & watch
npm run watch

# example start
npm start

Before commitment

# bundle
npm run build

Library

Deployment(git-flow)

# Checkout Release branch from `develop`
git checkout -b release/x.x.x

# Version Up
npm version major|minor|patch

# Publishes a package to the registry
npm publish

# Update master branch
git push origin release/x.x.x

# Push git tags
git push origin --tags

# Merge `release/x.x.x` into `master`

# Merge `release/x.x.x` into `develop`