* the performance from this is astounding
* help uws
* save 15 bytes in webpacks
* update readme
* why is markdown like this
* optimizations
* Update WebSocketManager.js
* friggin webpack tho
* probably important
* add all the stuff to the package.json
* add minify builds and a nice package.json script to run it all
* clean up
* use uglify harmony branch so we can actually run minify builds that work
* update build system
* make test better
* clean up
* fix issues with compression
*
* c++ requirements in a node lib? whaaaaat?
* fix travis yml?
* put railings on voice connections
* 🖕🏻
* aaaaaa
* handle arraybuffers in the unlikely event one is sent
* support arraybuffers in resolvebuffer
* this needs to be fixed at some point
* this was fixed
* disable filename versioning if env VERSIONED is set to false
* Update ClientDataResolver.js
* Update ClientVoiceManager.js
* Update WebSocketManager.js
* Update ConvertArrayBuffer.js
* Update webpack.html
* enable compression for browser and fix ws error handler
* Update WebSocketManager.js
* everything will be okay gawdl3y
* compression is slower in browser, so rip the last three hours of my life
* Update Constants.js
* Update .gitignore
* Add support for notes
* Ensure consistency with notes from ready payload
* Add getter method for users
* Minor tweaks
* Update warning messages
* More minor fixes
* add test for Client.destroy()
* propagate errors in ClientManager.destroy
If the promise returned by logout() rejects, previously
it would be completely uncaught, and just return an
eternally pending promise that never resolved.
* fix RESTMethods.logout
Without a data argument, the POST that superagent sends causes
the discord server to reply with a HTTP 400 error:
text: '{"Content-Type": "Expected Content-Type to be one of set([\'application/json\'])."}',
* fix Client.destroy
_timeouts and _intervals were changed to Set objects in
commit 6ede7a32fd a month ago.
Changing them to arrays causes failures if you try to reuse
the client object again.
* always close websocket in ClientManager.destroy
Invoking logout does not implicitly cause the server to close
the websocket for you, so cleanup everything.
Otherwise the websocket being open keeps node alive and hanging
mysteriously until the connection hits a timeout.
* fix indentation for eslint
* draft stuff
fix docstring for Client#token
Reorganise resolver
make env better for shards, clean up docs
Fix Gus' log messages
7
meh just gateway/bot not v7 :(
final changes, ready for mergin!
build docs
make default totalShards 'auto', fix docs for totalShards type
clean up docs more
run docs
* make consistancy real
* Update and rename getRecommendedShards.js to GetRecommendedShards.js
* Update GetRecommendedShards.js
* Update index.js
* Update RESTMethods.js
* Update Shard.js
* Update GetRecommendedShards.js
* Update ShardingManager.js
* run docs
* start blocking out client
* proto webhookclient
* wee working webhooks
* it's all working
* run docs
* fix jsdoc issues
* add example for webhookClient
* add example in the examples place
* fix docs
