A group of asteroids heading towards the Earth at very high speeds. Collision with any one of the would lead to extinction of all living beings on earth. Are you up to the challenge of saving Earth by destroing the asteroids.
Ato move leftDto move rightSpaceto shoot bullets
build - Directory for built and compressed files from the npm build script
src - Directory for all dev files
├── css - Contains all SCSS files, that are compiled to `src/public/css`
├── js - All the Three.js app files, with `app.js` as entry point. Compiled to `src/public/js` with webpack
│ ├── app
│ │ ├── components - Three.js components that get initialized in `main.js`
│ │ ├── helpers - Classes that provide ideas on how to set up and work with defaults
│ │ ├── managers - Manage complex tasks such as GUI or input
│ │ └── model - Classes that set up the model object
│ ├── data - Any data to be imported into app
│ └── utils - Various helpers and vendor classes
└── public - Used by webpack-dev-server to serve content. Webpack builds local dev files here.
└── assets - Is copied over to build folder with build command. Place external asset files here.
Install dependencies:
npm install
Then run dev script:
npm run dev
Spins up a webpack dev server at localhost:8080 and keeps track of all js and sass changes to files.
npm run build
Cleans existing build folder while linting js folder and copies over the public assets folder from src. Then sets environment to production and compiles js and css into build.
You can run any of these individually if you'd like with the npm run command:
prebuild- Cleans up build folder and lintssrc/jsclean- Cleans build folderlint- Runs lint on thesrc/jsfolder and uses the.eslintrcfile in root for linting ruleswebpack-server- Start up a webpack-dev-server with hot-module-replacementwebpack-watch- Run webpack in dev environment with watchdev:js- Run webpack in dev environment without watchbuild:dir- Copy files and folders fromsrc/publictobuildbuild:js- Run webpack in production environment