Tyler Hallada
4d1ef84568
Unfortunately, all of the train data has to be copied from the train web worker to the main thread on every tick so it knows the new positions of the trains to render. So every few ticks, the GC causes a little lag as it collects ~90+MB of obsolete train arrays. There's no way for the two threads to share the same data thanks to Spectre. |
||
|---|---|---|
| img | ||
| src | ||
| typings | ||
| .eslintrc.js | ||
| .gitignore | ||
| CNAME | ||
| index.html | ||
| LICENSE.txt | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| tslint.json | ||
| webpack.config.js | ||
Transport
Work-in-progress procedurally generated train network simulation written in Typescript with PixiJs.
Development
Clone the repo and then run:
npm install
npm start
Then visit http://localhost:8888 in your browser to view the development
build. Edit files in /src and see the changes reflected in the browser.
Test
No tests right now. But, to run lint checks:
npm run lint
Deploy
Run:
npm run build
npm run deploy