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

dreamt

v0.7.6

Published

Assorted reusable bits of game code and, aspirationally, a flexible, 3D, performant, networked game engine

Downloads

21

Readme

Dreamt

A thing I dreamt up to help me keep pace with my creative whims in the realm of 3D networked video games.

Probably not ready for anyone else to use.

Stands on the shoulders of open-source giants. Currently this list includes THREE.js, ECSY, CANNON.js (actually, the active ECMAScript fork, cannon-es) etc.

Designed to be friendly with FP rendering engines (e.g. React). See src/render/EntityRenderConnector.ts

Package Version Open Issues Build Status Coverage Status Dependencies Status Dev Dependencies Status Commitizen Friendly

Docs

click here for documentation and API reference materials

Contents

Developing

These steps need to be performed whenever you make changes:

  1. Write awesome code in the src directory.
  2. Build (clean, lint, and transpile): npm run build
  3. Create unit tests in the test directory.
  4. Verify code coverage: npm run cover:check
  5. Commit your changes using git add and git cz
  6. Push to GitHub using git push and wait for the CI builds to complete.

Note: This project uses automated changelog generation as long as you follow Conventional Commits, which is made simple through the included Commitizen CLI.

Releasing

Follow these steps to update the NPM package:

  1. Perform all development workflow steps including pushing to GitHub in order to verify the CI builds. You don't want to publish a broken package!
  2. Check to see if this qualifies as a major, minor, or patch release: npm run changelog:unreleased
  3. Bump the NPM version following Semantic Versioning by using one of these approaches:
    • Specify major, minor, or patch and let NPM bump it: npm version [major | minor | patch] -m "chore(release): Bump version to %s."
    • Explicitly provide the version number such as 1.0.0: npm version 1.0.0 -m "chore(release): Bump version to %s."
  4. The push to GitHub is automated, so wait for the CI builds to finish.
  5. Publish the new version to NPMJS: npm publish

Contributing

  1. Create a fork on GitHub
  2. Use the Suggested Development Workflow
  3. Create a GitHub pull request from your fork

Alternatively, (though less awesomely):

  1. Create an issue on GitHub
  2. Describe the issue in as much detail as possible. This makes up for not going the pull request route.
    • What happened
    • What did you expect
    • What browser/OS versions were you using
    • What have you tried to fix

Credits