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

@sjcrh/proteinpaint-client

v2.94.1

Published

a genomics visualization tool for exploring a cohort's genotype and phenotype data

Downloads

1,262

Readme

Proteinpaint Client

The client code for the ProteinPaint application

Installation

This should be installed as a workspace, follow the README at the project root.

Develop

From the proteinpaint/client directory:

npm run dev # generates bundles to public/bin
# the client dev script is usually called together with server start
# for St. Jude developers, that's `npm run dev` from the supermodule/parent repo

Test

You can view and run tests from http://localhost:3000, if you have a full dev environment running.


npm run test:unit
npm run test:integration

./test.sh *tvs.*.spec.*

# not recommended: `npm test` to run all available client-side tests.

## Build

```bash
npm pack

Release

Use Github Actions to coordinate the release of related package updates. The package versioning, build, and deployment uses the standard npm tooling under the hood (version, pack, and publish, respectively).