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

@superviz/sv-components

v0.12.131

Published

## Project setup ``` yarn install ```

Downloads

153

Readme

sv-components

Deploy

Project setup

yarn install

Storybook for development

yarn storybook:serve

How to commit on this project (Important)

Your commit messages are very important here and are used to release a minor or a major version automatically. You need to follow the conventions below:

fix: for a bug fix
chore: for simple things
feat: for a new feature

The commit message are also published on our Changelog, so please avoid fix: lint fix messages. :)

Run locally on Webapp project

First, build the sv-components project.

yarn build

And then go to nuxt.config.js on WebApp project and comment this line: '@nuxtjs/eslint-module',

Next, go to SvComponents.js on WebApp project and change the svComponents import to:

import SvComponents from '../../sv-components/dist/sv-components.common.js'

import '../../sv-components/dist/sv-components.css'

Note that the import are poiting to the locally sv-components dist folder. Make sure to set it to your local dist folder by tweaking the ../../ from the beginning.

Compiles and minifies for production

yarn build

Run your unit tests

yarn test:unit

watch test

yarn test:unit --watch

MacOS: Make sure to have watchman installed:

brew update
brew install watchman

Lints and fixes files

yarn lint

Releases

Before release a new version, create and set your GITHUB_TOKEN in your .env file with (important) package permissions.

You'll need to login in SuperViz GitHub registry using the command bellow. Use your token as your password when it is requested.

npm login -registry=https://npm.pkg.github.com -scope=SuperViz

Checkout the master branch and run the command below to check if it is all OK with your release:

yarn release:preview

It's all good? Go ahead and open your PR. A new version will be automatically released when you got approval to merge the PR on master.

Note: You can learn more about release-it here.