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

pixel-mask-generator

v1.0.1

Published

Procedural pixel generator

Downloads

4

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

jojoeejojoee

Keywords

pixelmaskgenerator

Readme

pixel-mask-generator

Travis Codecov Version - npm License - npm semantic-release

Very inspired and copy some code from zfedoran/pixel-sprite-generator

Note

  • [x] Compatible with all browsers
  • [x] Unit test: setup
  • [ ] Unit test: add more tests
  • [ ] Automated scripts: browser compatibility test
  • [ ] Automated scripts: deploy to gh-pages
  • [ ] Branch: split code from master and gh-pages
  • [ ] Dependency: split static/random.js to another repository
  • [ ] Dependency: split resize function to another repository
  • [ ] Travis
  • [ ] Codecov
  • [ ] Npm
  • [ ] Semantic-release
  • [x] Bower
  • [ ] Mask (square): add Square mask
  • [ ] Mask (square): add Star mask
  • [ ] Mask (square): add Circle mask
  • [ ] Mask (square): add Flower mask
  • [ ] Mask (square): add Square mask
  • [ ] Mask (square): add Square mask
  • [ ] Mask (horizontal): add Saber mask
  • [ ] Mask (horizontal): add Light saber mask
  • [ ] Mask (vertical): add Monkey mask
  • [ ] Mask (vertical): add Penguin mask
  • [ ] Mask (vertical): add Panda mask
  • [ ] Mask (vertical): add Butterfly mask
  • [ ] Mask (vertical): add Batman logo mask
  • [ ] Mask (vertical): add Christmas tree mask
  • [ ] Mask (vertical): add Bear mask
  • [ ] Mask (vertical): add Tank mask
  • [ ] Mask (vertical): add Plane mask
  • [ ] Mask (vertical): add Rocket mask
  • [x] Demo: create Demo page
  • [ ] Demo: update demo page
  • [ ] Coverage: increase coverage threshold
  • [ ] Article: copy original article into the repo, in case the site and mirror are down
  • [ ] Doc: installation
  • [ ] Doc: Example usage
  • [ ] Doc: Contribute
  • [ ] Doc: Contribute for owner
  • [ ] Algorithm: change algorithm toward to the original, should be symmetrical
  • [ ] Refactor: remove unused code

Contribute for owner

$ npm install -g semantic-release-cli
$ semantic-release-cli setup

Using above command to setup "semantic-release"

Contribute

  1. Fork the repo
  2. Install Node.js and dependencies
  3. Make a branch for your change and make your changes
  4. Run git add -A to add your changes
  5. Run npm run commit (don't use git commit)
  6. Push your changes with git push then create Pull Request

Reference