Consider using nodejs and "create react app" to manage the project.

[benjamin-heasly]

I've been wrestling somewhat with how to manage some of the nuts and bolts of our project. Things like:

• organizing code into modules
• importing dependencies like babylonjs and other libraries we might want
• writing and running tests
• loading files from disk without a lot of hoopla
• setting up a local server for testing and hot reloading

These things are pretty well settled in other language communities, like Java. But I'm learning that the Javascript world is more of a hipster hacker, browser wars, click bait, wild west kind of place, and these things are unsettled and potentially painful.

There is a tool set that would actually help with all of these things, with not much work on our part. It's called "create-react-app" and it works with a program that runs on each machine called nodejs. Maybe we should look at using this.

What's weird about it is, "create-react-app" is intended for making web pages using a framework called React. We're not trying to do that! But the tool brings so many other nice things, like modules, tests, and local hot reloading, that I'm still tempted to use it.

I think this would be supported well on any OS and probably even integrates well with Atom. But it might be overkill and would be somewhat of a mental shift for us. So...just a thought to think about.

[RobotPrototype]

I definitely see those roadbumps on the horizon and agree we should develop a strategy for dealing with them. I think that I trust your intuition about what looks helpful, for what its worth.

I'll look into the React thing!

[RobotPrototype]

in what ways might this be overkill? I am having some trouble wrapping my head around the whole organizational aspect, but this seems like a useful suite of tools.

does it seem like it is going to try and push us toward React? Or will we easily be able to just take what we want from it.