Skip to content
This repository has been archived by the owner on Jul 23, 2024. It is now read-only.

cava-cava/client

Repository files navigation

"CA VA - CA VA"

TypeScriptReactReduxReact Three FiberSocket.IONode

Getting Started

Prerequisites

  • npm
    npm install npm@latest -g

Installation

  1. Clone the repo
    git clone [email protected]:happy-game/client.git
  2. Install NPM packages
    npm install

Available Scripts

npm run develop

Runs the app in the development mode. Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits. You will also see any lint errors in the console.

npm run start | npm run server:start

Runs the app / server in the production mode. Open http://localhost:8080 to view it in the browser.

npm run server:watch

Run a compile based on a backwards look through the server index.ts with the compiler defaults.

The file will reload if you make edits.

npm run server:build

Run a compile based on a backwards look through the server index.ts with the compiler defaults.

npm run server:dev

Runs the server in the development mode.

The server will reload if you make edits.

npm run server:debug | npm run server:debug:all

Runs the server in the development mode.

The server will reload if you make edits. You will also see any all server errors in the console.

npm run server:debug:socket

Runs the server in the development mode.

The server will reload if you make edits. You will also see any socket.io server errors in the console.

npm run server:debug:engine

Runs the server in the development mode.

The server will reload if you make edits. You will also see any socket.io/engine server errors in the console.

npm run build

Builds the app for production to the build folder. It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes. Your app is ready to be deployed!

See the section about deployment for more information.

npm run test

Launches the test runner in the interactive watch mode. See the section about running tests for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.