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

@visao/viewer-api

v0.0.1-beta.18

Published

Visao viewer api

Downloads

350

Readme

Visao Viewer API

Installation

Install needed dependencies of the project.

yarn install

Tests

yarn test

Build

yarn build

Deploy new version

The first thing to do is to make sure everything is committed. Meaning there are no git pending changes. Once that is done, we need to determine what kind of release we are making (Patch, Minor, Major). Here is a fun article to help us determine what to do.

Patch

Content: Internal fix

Example: Bug fix, Performance improvement, environment or internal tweaks

Policy: Consumers should update their software without hesitation

yarn patch

Minor

Content: Interface change with full backward compatibility

Example: New feature, Endpoint declared deprecated

Policy: Update your software to get some new features. Nothing will break

yarn minor

Major

Content: Interface change breaking backward compatibility

Example: Change API endpoint name or signature, Remove an endpoint

Policy: Test your system extensively post update. Migration documents may be in order

yarn major

Publish on npm

yarn publish

Issue Tracking

Check this repo to see all the reported issues from our users.