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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@vecnacares/vc-ui

v0.0.10

Published

Vecna Cares UI Components

Readme

#Author: Mohit

vc-ui

Vecna Cares UI Components based on Material UI

Pipeline Coverage NPM JavaScript Style Guide

Install

yarn add @vecnacares/vc-ui

Usage

import React, { Component } from 'react';

import { VcButton } from '@vecnacares/vc-ui';

class Example extends Component {
  render() {
    return <VcButton value="Click Me" />;
  }
}

Gitlab workflow

  1. Make sure you have a gitlab account.
    • Optionally set up ssh keys for your convenience. See https://docs.gitlab.com/ee/gitlab-basics/create-your-ssh-keys.html
  2. Clone or pull most recent changes
    • If it's the first time working on this project, clone it git clone [email protected]:VecnaCares/vc-ui.git
    • Otherwise pull the most recent changes git checkout master && git pull --rebase
  3. Create a branch. The name of the branch should reflect the issue you are working on. This is usually the Jira ID. For example IDE-1234
  4. Make changes and push to the branch. git push origin <branchName>
  5. Open a merge request by either following the link in the git console or following instructions outlined here https://docs.gitlab.com/ee/gitlab-basics/add-merge-request.html
  6. Add reviewer(s)
  7. Once the review is done, merge the code into the master branch

Development

  • The src directory contains all the components
  • The example directory contains examples of using the components defined in src
  • Run yarn start to compile and watch changes in the src directory
  • Run yarn styleguide to start the styleguide server for component documentation
  • Run cd example && yarn start to start and watch development server in the example directory
  • Test can be run by running yarn test
  • Code will be automatically formatted by prettier on each commit

Using unpublished changes in example

The example subproject has dependency on vc-ui. To test changes made to vc-ui without publishing them to npm, we have to link the vc-ui package.

Linking

First, in the vc-ui folder (where package.json is):

npm link

Then in the example folder link the module:

npm link @vecnacares/vc-ui

Unlinking

To revert to the published version on npm, run the following in the example directory

npm unlink --no-save @vecnacares/vc-ui

Next, in vc-ui directory

npm unlink

Documentation

We use style react styleguidist to document components.

Read how to document components here

Documentation is published on gitlab pages here and the components demo is here

License

MIT © VecnaCares