React mp3 Player

An Mp3 player to play any audio file based on ReactJS

Table of Contents

• Installation
• Usage
• Adding-new-icons-to-the-library
• Contributing

Installation

Install via NPM

npm install react-mp3-player

or use yarn

yarn add react-mp3-player

Usage

Import the Icon component

import {Player} from 'react-mp3-player';

Add the Player component and pass it the relative mp3 playlist as well as a primary and secondary color

<Player playlist={['audio.mp3', 'audio2.mp3']} primaryColor='#FFFFFF' secondaryColor='#FEFEFE'/>

Adding new features to the mp3

Make any changes or additional features in the Player.js component and update the version (in the package.json) by 0.0.1 and then push all your changes to the repo.

Publish to NPM

Firstly make sure to build to the dist folder. Run

yarn build

Then publish the update to npm by running

npm publish

Your update should now be live on NPM. Make sure to update the package in your project by running

yarn upgrade react-mp3-player

Contributing

Download the repo to your machine

git clone https://github.com/in-touch-dev/intouch-mp3-player

Then to get up and running with a dev environment

In the project directory, you can run:

yarn start

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.

yarn test

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

yarn 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.

yarn 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.