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

@footgun/planck

v0.2.3

Published

2D JavaScript/TypeScript physics engine for cross-platform HTML5 game development

Downloads

304

Readme

@footgun/planck

This is an independently maintained fork of Planck.js at v1.0.6

Why the fork?

There are 2 main reasons:

  1. Use array notation for Vectors instead of Objects.
  2. Vectors should be pure data, rather than having every single vector instance a class with dozens of methods attached.

Planck way:

import { Vec2 } from 'planck'

const p = new Vec2(50, 50)   // generates an Object Oriented monstrosity
console.log(p)    // { x: 50, y: 50, ...pile o' functions }

I use array notation in my projects, so I want to declare vectors like this:

import { Vec2 } from '@footgun/planck'

const p = Vec2.create(50, 50)  // generates pure data
console.log(p)   // [ 50, 50 ]    A nice simple array.  You know, like, data.  :)

These 2 changes make it possible to re-use other popular libraries for vector/matrix math. Vectors produced by gl-matrix and wgpu-matrix are fully interoperable with this physics engine.

References

You can find the original library here.

All of the same examples and documentation should be the same for this port, except for constructing Vec2 and Vec3 instances.

For a fantastic, compatible Vector/Matrix/Math library check out wgpu-matrix