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

@code-dot-org/dance-party

v2.0.0

Published

[![Build Status](https://github.com/code-dot-org/dance-party/actions/workflows/build.yml/badge.svg?branch=main)](https://github.com/code-dot-org/dance-party/actions/workflows/build.yml) [![codecov](https://codecov.io/gh/code-dot-org/dance-party/branch/mai

Downloads

3,566

Readme

Dance Party

Build Status codecov

Steps to get up and running

git clone [email protected]:code-dot-org/dance-party.git
cd dance-party
nvm install
nvm use
yarn
yarn run dev

At this point the app will be running at localhost:8080. Open the developer tools in Chrome and you can access the API via nativeAPI.*

If you want to make changes locally in dance-party and have them show up in your apps build, do the following:

  • In the code-dot-org/apps directory, run yarn link <path to dance-party>

For example if your dance-party and code-dot-org projects are stored in your root directory, you would run yarn link ~/dance-party. Note that there will be local changes in package.json and yarn.lock that you want to make sure you don't commit.

To debug unit tests in the Chrome debugger: node --inspect --debug-brk ./node_modules/.bin/tape ./test/unit/*.js Open chrome://inspect in Chrome browser (requires Chrome 55+) Tap on inspect link under "Remote Target"

Additional build notes

Node 14.17.1 or higher should be used. This can be achieved by running:

nvm use v14.17.1

It also appears that Python 2.7 should be used and must be available for installing node-gyp. Techniques may vary, but this worked in one situation:

apt-get install python2.7
ln -s /usr/bin/python2.7 /usr/bin/python

Adding New Characters

To add a new character to Dance Party, follow the instructions here: https://github.com/code-dot-org/dance-spritesheets to create the spritesheet for the character.

Effects Testing

yarn run test:visual uses pixelmatch to test for consistency in screenshots between your local branch and an accepted baseline. Accepted baselines are saved in test/visual/fixtures. To debug a test failure, run node ./test/visual/helpers/generateScreenshot.js <effectName> <pathToDirectory> to output the local screenshot to the given directory. If a baseline does not exist for a given effect, the screenshot from your local branch is saved as the baseline. Effects are drawn with no characters on the screen so effects appear the same when drawn as backgrounds or foregrounds.

To Add Test Coverage For a New Effects

Add the name of the effect to the list of effects in backgrounds.js. Run yarn run test:visual. After a new baseline is generated, manually inspect it to ensure it matches expectations.

To Update A Baseline

Delete the accepted baseline. Run yarn run test:visual. After a new baseline is generated, manually inspect it to ensure it matches expectations.

Publishing a new version

First, ensure you have the main branch checked out locally, and that it's up to date.

To publish a new version, the following command should work:

yarn version 1.0.4

With 1.0.4 replaced by the new version number that should be published.

Note: make sure you are logged into npm first. If not, the command may fail with a misleading E404 error. You can see if you're logged in with yarn npm whoami, and if not logged in, can can use yarn npm login.