From 6e5d1781a6cfe55a5da96fefd819994d2c7707f4 Mon Sep 17 00:00:00 2001
From: Alec
@@ -35,11 +33,7 @@ The application prioritizes responsiveness. A key scenario would be when a group
## Tech Stack
This is a Node.js application. It is written purely using JavaScript/HTML/CSS. The main dependencies are
-Express.js and Socket.io. It is fully open-source
-and under the MIT license. This was (and still is) fundamentally a learning project, and thus I welcome collaboration
-and feedback of any kind.
-
-All pixel art is my own, for better or for worse.
+Express.js and Socket.io.
## Contributing and Developers' Guide
@@ -62,10 +56,10 @@ This command uses nodemon
to listen for changes to **server-side code** (Node.js modules) and automatically restart the server. If you do not want
this, run instead `npm run start:dev:no-hot-reload` or `npm run start:dev:windows:no-hot-reload`.
-If you are developing as well, in a separate terminal, execute `npm run build:dev`. This uses
+If you are making changes to client-side javascript, in a separate terminal, execute `npm run build:dev`. This uses
Webpack to bundle javascript from the `client/src` directory and place it in the `client/dist` directory, which is ignored by Git.
This command uses the `--watch` flag, which means the process will continue
-to run in this terminal, watching for changes to JavaScript within the `client/src` directory and re-bundling automatically. You
+to run in this terminal, watching for changes within the `client/src` directory and re-bundling automatically. You
definitely want this if making frequent JavaScript changes to client-side source code. Any other changes, such as to HTML or CSS
files, are not bundled, and thus your changes will be picked up simply by refreshing the browser.