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

story2frontify

v0.0.5

Published

> This is currently alpha. Not every scenario has been looked into. If you find something, please raise an issue or PR.

Downloads

10

Readme

Story2frontify

This is currently alpha. Not every scenario has been looked into. If you find something, please raise an issue or PR.

About

Convert your stories inside storybook to frontify's pattern library.

Installation

This can be installed globally or local to your repo.

Inside project:

npm i --save story2frontify

Globally:

npm i -g story2frontify

Usage

Pass the arguments:

  • token
  • project
  • baseUrl
  • localhost (default: http://localhost:9001/iframe.html)
  • input (if you want to use static storybook instead)

Examples:

 s2f --token xxxxxxxxxxxx --project xx --baseUrl https://PROJECT.frontify.com
 s2f --token xxxxxxxxxxxx --project xx --baseUrl https://PROJECT.frontify.com --localhost http://localhost:8080/iframe.html
 s2f --token xxxxxxxxxxxx --project xx --baseUrl https://PROJECT.frontify.com --input dist/demo/iframe.html
 export token='xxxxxxxxxxxxx'
 export project='xx'
 export baseUrl='https://PROJECT.frontify.com'
 s2f
 export token='xxxxxxxxxxxxx'
 export project='xx'
 export baseUrl='https://PROJECT.frontify.com'
 s2f --input dist/demo/iframe.html

issues

Each story needs to have a div wrapper around.

Currently to decide if your stories are an atom, molecules, organisms, page or template you need to have a a type attribute in the first (primary) story.

return ('<div type="atom"><button>Click me</button></div>');