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

@molgenis-experimental/molgenis-app-pipeline-dashboard

v1.1.3

Published

[![Commitizen friendly](https://img.shields.io/badge/commitizen-friendly-brightgreen.svg)](http://commitizen.github.io/cz-cli/)

Downloads

8

Readme

Commitizen friendly

molgenis-app-pipeline-dashboard

Dashboard for following the status of running pipelines. Each run has to go through multiple steps to complete which can take a lot of time. When errors occur you want to know as quickly as possible where the problem lies.

Setup in MOlGENIS for production:

proxy MOLGENIS pipeline dashboard or @molgenis-experimental in MOLGENIS instance from unpkg https://unpkg.com/@molgenis-experimental/molgenis-app-pipeline-dashboard/dist/index.html

Menu manager -> add menu item -> plugin select redirect

query parameter: url=my.domain.nl/@molgenis-experimental/molgenis-app-pipeline-dashboard/dist/index.html

Prerequisites

MOLGENIS docker or a MOLGENIS server is required to run the application

git clone https://github.com/molgenis/docker.git

cd docker/molgenis/8.2

docker-compose up

data

Demo data available Data and upload to MOLGENIS docker or other MOLGENIS server using data import

Project setup

yarn install

config for development

Change the proxy settings in vue.config.js to correspond to your molgenis instance:

//vue.config.js
proxy: process.env.NODE_ENV === 'production' ? undefined : {
      '^/api': {
        target: 'localhost:8081', //molgenis docker default change to actual
        changeOrigin: true
      },
      '^/login': {
        target: 'localhost:8081', //molgenis docker default change to actual
        changeOrigin: true
      }
    }

configure table locations in src/store/state.ts:

state = {
  overviewTable: 'status_overview', //status_overview
  projectsTable: 'status_projects', //status_projects
  jobTable: 'status_jobs', //status_jobs
  timingTable: 'status_timing', //status_timing
  sampleTable: 'status_samples', //status_samples
  clusterTable: 'status_clusters', // status_clusters
  ...
}

Compiles and hot-reloads for development

yarn run serve

then navigate to localhost:8080

Running unit tests

yarn test:unit

Generating code documentation for typescript files

yarn typedoc src

results can be found at docs/documentation/index.html

Customize configuration

See Configuration Reference.