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 🙏

© 2025 – Pkg Stats / Ryan Hefner

burner

v3.1.7

Published

A DOM-based rendering engine.

Downloads

4

Readme

Build status

#Burner: A rendering engine for DOM-based animation.

Use Burner to setup a DOM-based rendering system in a web browser. Burner supplies some convenient functions for controlling playback, controlling the camera, detecting world boundaries, and optimizing object management via object pooling.

##Install

To include Burner as a component in your project, use the node module.

npm install burner --save

You can also use the standalone version and reference both the css and js files from your document.

<html>
  <head>
    <link href="css/burner.min.css" type="text/css" charset="utf-8" rel="stylesheet" />
    <script src="scripts/burner.js" type="text/javascript" charset="utf-8"></script>
  </head>
  ...

##Usage

Burner contains the essential classes for creating a rendering engine... System, World and Item. You can use these built-in classes to create simple systems.

<!DOCTYPE html>
<html>
<head>
  <link rel="stylesheet" href="css/burner.min.css" type="text/css" charset="utf-8" />
  <script src="scripts/burner.js" type="text/javascript" charset="utf-8"></script>
  </head>
  <body>
    <script type="text/javascript" charset="utf-8">
      Burner.System.setup(function() {
        this.add('World');
        this.add('Obj');
      });
      Burner.System.loop();
    </script>
  </body>
</html>

Using your own classes

To create something more complex, you need supply a library of classes like FloraJS that inherit from the Item class.

A class must meet some minimum requirements:

  • It must extend the Burner.Item class via Burner.Utils.extend. (ie. Burner.Utils.extend(Obj, Burner.Item))
  • It must call Burner.Item in its constructor. (ie. Burner.Item.call(this))

You must add an entry for your class in Burner's 'Classes' map. Call setup() and pass a function that adds an instance of your class. Finally, call loop().


<!DOCTYPE html>
<html>
<head>
  <title>Burner | Custom classes</title>
  <link rel="stylesheet" href="css/Burner.min.css" type="text/css" charset="utf-8" />
  <script src="scripts/Burner.min.js" type="text/javascript" charset="utf-8"></script>
  </head>
  <body>
    <script type="text/javascript" charset="utf-8">

      /**
       * Creates a new Obj.
       *
       * @param {Object} [opt_options=] A map of initial properties.
       * @constructor
       */
      function Obj(opt_options) {
        Burner.Item.call(this);
        this.name = 'obj';
      }
      Burner.Utils.extend(Obj, Burner.Item);

      // Uncomment to provide your own step function.
      /*Obj.prototype.step = function() {
        // your code to update this obj every frame goes here
      };*/

      /**
       * Tell Burner where to find classes.
       */
      Burner.System.Classes = {
        Obj: Obj
      };

      /**
       * Create a new Burner system.
       */
      Burner.System.setup(function() {
        this.add('World', {
          color: [200, 200, 200]
        });
        this.add('Obj', {
          color: [0, 0, 0]
        });
      });
      Burner.System.loop();
    </script>
  </body>
</html>

Running the code, you should see a black box fall to the ground. The Item class has a default step() function that runs a gravity simulation.

You can override the default step() function to control your object's behavior any way you want.

##Docs

To learn more, please review the docs.

Building this project

This project uses Grunt. To build the project first install the node modules.

npm install

Next, run grunt.

grunt

To run the tests, run 'npm test'.

npm test

To check test coverage run 'grunt coverage'.

grunt coverage

A pre-commit hook is defined in /pre-commit that runs jshint. To use the hook, run the following:

ln -s ../../pre-commit .git/hooks/pre-commit

A post-commit hook is defined in /post-commit that runs the Plato complexity analysis tools. To use the hook, run the following:

ln -s ../../post-commit .git/hooks/post-commit

View the code complexity report.