The ChipPP plays music from Spotify and videos YouTube. It raises the corresponding window whenever a song/video comes on. Songs/Videos can be queued by anyone.
In the project directory, you can run:
Starts the server application that manages the music and videos and provides the API for the webapp.
Starts the React webapp.
Starts both the server application and the React webapp.
Launches the test runner in the interactive watch mode.
See the section
about running
tests for more
information.
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.
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.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.