jacekpietal


Jacek Pietal

  • a *very* slim package for basic DOM operations - few bytes

    published 1.4.2 5 years ago
  • Tiled Utils for Pixi.js - usable with node.js with pixi-shim

    published 5.1.0 2 months ago
  • pixijs shim for backend use of pixijs

    published 2.5.3 23 days ago
  • detecting collisions between bodies: Points, Lines, Boxes, Polygons, Ellipses, Circles. RayCasting. Bodies have offset, rotation, scale, bbox padding, be static (non moving), be trigger bodies (non colliding).

    published 9.8.0 16 days ago
  • Dont allow your fluffy memleak to grow, Fluffy detects memleaks

    published 1.1.0 4 years ago
  • PIXI.js Tiled utilities

    published 2.0.3 2 years ago
  • simple, zero-dependency, in-memory, lazy cache for javascript

    published 2.0.1 a year ago
  • Auto make folders for routes and copy index.html - all from sitemap.xml

    published 1.1.0 4 years ago
  • prodecural dungeon generator for games

    published 1.0.1 a year ago
  • µwebsockets.js npm package fork of: https://github.com/uNetworking/uWebSockets.js

    published 19.0.0-docs 3 years ago
  • zero-dependency Object Pool manager for instantiating, getting, reuising and destroying objects in javascript

    published 1.1.0 3 years ago
  • a 2024 version of stats.js + gstats

    published 1.3.6 22 days ago
  • Show DrawCalls, FPS, Texture Count on PIXI, Phaser projects

    published 0.1.2 2 months ago
  • Get your AWS credentials and place them where [aws-sdk](https://www.npmjs.com/package/aws-sdk) package needs them: [docs.aws.amazon.com](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html)

    published 1.2.0 2 years ago
  • chef-js + express = static files server

    published 2.1.4 23 days ago
  • chef-js + express + socket.io = static files server + websockets

    published 2.1.4 23 days ago
  • chef-js + uWebSockets.js = static files server + websockets

    published 2.1.4 23 days ago
  • chef-js core functionalities

    published 3.0.6 23 days ago
  • service worker for pwa - use fresh then cache response

    published 1.0.1 a year ago
  • when your node.js process uses too much memory, allow it to gracefully exit

    published 1.3.0 a year ago