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

bowser-cli

v0.0.0

Published

A command line interface to create bowser-engine based games with ease.

Downloads

5

Readme

BOWSER-CLI

Enquiring

Bowser-cli is a command line interface made to simplify the creation of games based on bowser-engine.

Bowser-cli is a node package meant to be installed and used globally. To have a good idea of how it should be used pleased refere to this article.

Collaborate

We are very kean to have people contributing to the project, whether it is by pointing at issues, sharing ideas, issuing pull requests or ultimatly becoming official members. That being said, good collaboration does not go well without clear guidelines and organisation. This is why we will take advantage of this readme to outline some of that stuff.

  • Indentation is made out of four spaces.
  • Code is formated matching JSLint standards.
  • In line documentation follows JSDoc markup.
  • Comments are one liners starting with a capital and ending with a dot.
  • Git commits are one liners starting with a capital and ending without ponctuation.
  • A base class becomes folder. Sub-classes live in that folder.
  • We host a single class per source file.
  • Source files export the class itself.
  • When a package is required it is declared uppercase.

It goes without saying that all guidelines are up for discussions. If something can be done in a way that is substantialy better, there is no reason to keep doing it.