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

vispa

v0.0.3

Published

[![build status](https://git.rwth-aachen.de/3pia/vispa/badges/master/build.svg)](https://git.rwth-aachen.de/3pia/vispa/commits/master)

Downloads

6

Readme

VISPA

build status

Development

Development process

We should follow a git workflow with feature and release branches, and release and release candidate tags.

Features and bugfixes
  • The master branch is protected and should be kept clean and up-to-date.
  • For features, fixes, etc, create feature branches based off the master branch.
  • Create merge requests to merge your (tested) feautures back into the master branch.
Releases
  • For preparing a release, we create a release/v<major>.<minor> branch based off the master branch.
  • Tags of commits on release branches are named v<major>.<minor>.<patch>-<stage>, where the first patch number is 0 and the stage is typically rc0, rc1, etc.
  • Use branches prefixed with hotfix/ to fix bugs in release branches.
  • When a release is ready to be published, we create a new tag named v<major>.<minor>.<patch>.
  • The changes due to hotfixes should be added to the master branch again by either
    • merging without fast-forwarding, or
    • cherrpy-picking certain commits from hotfix branches.
Release and tag versioning
  • Release branches: release/v<major>.<minor>
  • Tag on release branches: v<major>.<minor>.<patch>-<stage>
  • All other tags must not start with v\d.
Branch naming

Except for the master branch, we should use the <purpose>/<description> convention.

purpose should be one of the following:

  • <username> for personal branches.
  • feature for feature branches.
  • fix for bug fixes on the master branch.
  • release for final releases (with description as defined above).
  • hotfix for bug fixes on release branches.

Docker

You can find all images at our Docker Hub.

We provide a dedicated image containing everything to run the vispa server. This image can also be used for development:

# checkout VISPA
git checkout [email protected]:3pia/vispa.git
cd vispa

# run the server inside docker
docker run --name vispadev -ti -p 4282:4282 -v `pwd`:/vispa/repo 3pia/vispa-server
  • --name vispadev names the container "vispadev" so you can start and attach it later on without looking up the hash.
  • -ti allocates a pseudo-tty and keeps stdin open.
  • -p 4282:4282 publishes the application port (second number) to the host system (first number).
  • -v `pwd`:/vispa/repo mounts the current host directory to the container directory that is supposed to contain the vispa repository.

The container is not deleted when you stop it (no --rm parameter). If you want to reattach it to start developing again, do:

docker start vispadev && docker attach vispadev

TODO

Hooks

  • server.setup
  • server.listen
  • socket.started
  • db.connection.established
  • db.models.loaded
  • user.register, user
  • user.login, user
  • workspace.add, workspace, user