Ashxn

I agreed it was a problem. The reason I don't particularly like the `static name` approach is that it requires you to name the component twice. It's cumbersome and what...

Yeah for now it's just using some hardcoded defaults. It could probably have a method `world.presentation.configure(options)` to rebuild the WebGLRenderer/Camera/Scene etc based on some options if needed

I'd be happy to update `hecs-plugin-three` to support replacing the scene, camera, renderer etc using this flow https://github.com/gohyperr/hecs/pull/26#issuecomment-730060336 And if the option doesn't exist it just falls back to what...

Yeah I haven't gotten around to it yet. Personally I don't run into this much because i've been using it for a long time and must know how to avoid...

These are the steps I took to create a reproduction: 1. Edit the `hecs-plugin-core` package `WorldTransformSystem` and insert a `throw new Error('LOL')` into the `update()` function 1. Run `yarn build`...

@canadaduane if this works for you, lets remove the `files` change and then I can merge

They're useful but i agree they're noisy in tests. I'm not sure of an easy way to suppress them. Any ideas?

That's really weird. I just double checked, in the `master` branch all the packages dependencies are set to 0.14.0 and all the published Npm packages are also at 0.14.0 I...

Oh no you're right. It looks like the release script is somehow changing the version after its published not before :P

When we make a release of all the hecs packages we run `yarn release` from the root directory. This uses lerna to bump versions and then publishes to Npm. Lerna...