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

byond-infinity-lib

v1.39.0

Published

Byond Infinity Lib

Downloads

24

Readme

Infinity UI Library

Codefresh build status

codecov

Live Demo

Component Structure & process to add new component

  1. Components -> new component Name
  2. .stories.js file for stories
  3. .test.js file to test renderer
  4. Components/v1 -> for next-ui

Install (assuming you are inside lib directory)

 npm i

Run (Local)

npm run storybook

Publish

Travis will publish it for you once you commit/merge to master.

bash .travis-build.sh
bash run.sh

Release

Note: Package.json version is set to 0.0.0-semantically-released since release is been managed by semantic-release

Commit message type

fix: A bug fix
docs: Documentation only changes
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
refactor: A code change that neither fixes a bug nor adds a feature
perf: A code change that improves performance
test: Adding missing or correcting existing tests
chore: Changes to the build process or auxiliary tools and libraries such as documentation generation

Easy way to do conventional commit

npm run commit

Run Components (Docker)

from parent dir run following command, to build docker image

docker build -t test -f ./infra/docker/Dockerfile ./lib

to run

docker run -p 80:80 test