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

Docs

click here for documentation and API reference materials

Contents

• Suggested Development Workflow
• Releasing New Code
• Contributing
• Credits

Note: Physics, if desired, can be wired up using @react-three/cannon within react-three-fiber components.

PS: Until #124 is merged I recommend using my fork of @react-three/cannon.

Developing

These steps need to be performed whenever you make changes:

0. Write awesome code in the src directory.
1. Build (clean, lint, and transpile): npm run build
2. Create unit tests in the test directory.
3. Verify code coverage: npm run cover:check
4. Commit your changes using git add and git cz
5. 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:

0. 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!
1. Check to see if this qualifies as a major, minor, or patch release: npm run changelog:unreleased
2. 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."
3. The push to GitHub is automated, so wait for the CI builds to finish.
4. Publish the new version to NPMJS: npm publish

Contributing

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

Alternatively, (though less awesomely):

0. Create an issue on GitHub
1. 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

• @chriswells0
  • the fantastic Typescript node package template used as a starting point