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

eacy

v0.1.2

Published

Helper package for `eaciest`

Downloads

12

Readme

Eacy

Helper package for eaciest

Currently, provides HMR support for systems and data.

Example usage:

Add eacy loader to webpack config:

// webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        // using specific filename here to limit the loader runs
        test: /hmr\.js$/,
        loader: 'eacy',
      }
    ]
  },
};

Define HMR setup function:

// hmr.js

export const initHMR = (engine) => {
  // Following comments will be substituted with HMR code

  // setupContentPath systems ./systems engine
  // setupContentPath data ./data engine
}

The comments will result in import of all the systems placed under ./systems/** path and also all the data files from ./data/** path.

Note the engine argument. It has to be defined in the comments to generate proper HRM code. It will be used for (un)registering all the systems and data entries.

After that create your system and data files:

// systems/my-system.js

import { System } from 'eaciest';

export default class MySystem extends System {

  constructor () {
    super([
      'position',
      'velocity'
    ]);
  }


  update (dt) {
    for (const entity of this.getEntities()) {
      entity.position.x += entity.velocity.x * dt;
      entity.position.y += entity.velocity.y * dt;
    }
  }

}
// data/player.js

const playerData = {
  position: { x: 100, y: 100 },
  velocity: { x: 0, y: 10 },
}

export default playerData;

Lastly, call the initHMR we defined earlier, with your engine instance. This will load the system and the player data to your it. Try changing them to see the changes being hot-reloaded.