|Number of watchers on Github||106|
|Number of open issues||1|
|Average time to close an issue||less than a minute|
|Open pull requests||0+|
|Closed pull requests||0+|
|Last commit||about 4 years ago|
|Repo Created||about 5 years ago|
|Repo Last Updated||about 1 year ago|
|Organization / Author||krimple|
|Do you use angular-socketio-chat? Leave a review!|
|View angular-socketio-chat activity|
|View TODOs for angular-socketio-chat (29)|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Trendy new open source projects in your inbox! View examples
Sample AngularJS + NodeJS/Express application demonstrating the use of Socket.IO. I am using:
This project was a simple test of sockets as a traditional (some might say 'ye olde') chat program. I wanted to write it as angularly as possible (is that really a word?) and use the traditional Grunt-based workflow of Yeoman where possible.
At some point I need to take a day and convert this over to a more comprehensive script with gulp. Ah, todo todo...
I am not using Node at this point for anything more than a chat websocket server, however now you're nicely set up for an /api (see the /route directory and js file for a stupid JSON example).
I have the root
app.js node script pointing to serve / as the content
in /angular-frontend/app/ - you can construct and build and minify with
grunt --force in the
angular-frontend directory. This will set the
/public to the minified version of the application and you
can serve that by editing
To launch the app and run in development mode:
app.js file and swap the commented and uncommented lines that
serve the static content.
Run the build:
cd angular-frontend grunt --force cd .. node app.js
http://localhost:3000and you should see the chat client using minified scripts.