Releases: serversideup/amplitudejs
Releases · serversideup/amplitudejs
v3.1.0
New Features
- Officially added browser support to README (#71)
- We included an official minified version of
amplitude.js
in the/dist
directory (#68) - We now have example players for you in the
/examples
directory (#87) - Added Pause Callback (#37)
- Add method to expose setting track time as percentage (#81)
- You can now move to next or previous song by using
Amplitude.next()
,Amplitude.prev()
,Amplitude.next( playlistIndex )
, orAmplitude.prev( playlistIndex )
(#103) - Every user settable variable in the config has a getter and a setter publicly exposed. This will give full control at all times to the developer/designer of the functionality of AmplitudeJS. (#80)
Bug fixes
v3.0.2
Bug Fixes
- Fixed bug in NPM where it was requiring a global install
Important Notes
- Nothing in the
amplitude.js
file changed fromv3.0.1
. Only required a version bump to fixnpm
v3.0.1
New Features
- Complete code-base restructure focused on modern Javascript development techniques and
bundled together using webpack. There is little to no migration necessary from 2.0 to 3.0. - Playlists: All of the media on the page can be organized into playlists through the songs array
- Multiple Playlist Support: Multiple playlists can share the same page
- We made it much easier on how to contribute to the AmplitudeJS project
Bug Fixes
- Numerous, numerous bug fixes
Removed
- Web Audio API visualization capability: This will be re-added as a plugin in future releases
with more flexibility and control of the visualizations.
v2.2.0
New Features
- Added Repeat Functionality and Autoplay
- Made AmplitudeJS a little more flexible for allowing for multiples of buttons with attribute ids to determine functionality.
v2.0.0
New Features
- Modularizes the script
- Soundcloud support
- Web Audio API support
v1.0.0
This is the original release of AmplitudeJS. We will be releasing a completely rewritten AmplitudeJS with a ton of new features. Even though 1.0 was originally published back in April of 2014, we wanted to make sure we kept the original release in an easy to find spot as we move onto AmplitudeJS 2.0.