These must now be passed to the .connect() function instead.

Could add annotations to most things, I guess.

You can set the cycle/lock state, but not access it easily.

Maybe somethin like

mp.isCycling()
mp.isLocked()

They exist but are not documented: https://github.com/goto-bus-stop/miniplug/blob/master/src/plugins/history.js

Version 2.4.0 of debug just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As debug is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Since the other mod* events on plug.dj are also mod* events in miniplug.

mp.dj() return undefined if the actual dj is bot.
it's normal things, a bug or i'm just bad ???

Hi!
I'm using miniplug to set up my bot, and I am facing an issue. After registering this :
mp.on('advance', eventAdvance);
and
function eventAdvance(next, previous) { console.log(previous.score.positive); }
I have an error telling me that previous.score is undefined.

Please answer me ASAP, thanks :)

To prevent getting locked out of plug.dj because of rate limiting, API requests should be spaced out somewhat.

Can use the /_/profile/${id} endpoint now for a mp.user(xyz).getHistory() method.

Using Ava and Nock. Will have to run Ava in --serial mode but that's ok :)

Sometimes (often when plug is having issues) the bot can login but not connect to the socket. This leaves the bot useless and if you run stuff like forever monitor, your bot won't reconnect.

Perhaps a constant monitor of events to make sure the bot is connected could be a method to fix this. Or maybe some type of check after login.

Some properties are named .time (current history entry), while others are .timestamp (notifications). Should pick one and stick with it.

Instead force people to use .connect(options).

v1.x:

const mp = miniplug({ email: '[email protected]', password: 'abc' })

Proposed v2.x:

const mp = miniplug()
await mp.connect({ email: '[email protected]', password: 'abc' })

This so we have a clear hook for login/connection failures.

After advance fires, historyEntry is rebuilt in a different format than history (which also doesn't include the assistance methods such as the newly-added skip()).

Just the other day, plug was having issues with advancing and whatnot. When the site went down (or perhaps before?), my bot didn't get any type of error, plugMait, etc. event. It just stopped receiving all events from plug.

This is an issue since my bot had no way of knowing plug was down and therefore couldn't auto restart. There should be some kind of timeout where it'll emit an event that there haven't been any events from plug after x amount of time. (probably 30s~1m)

There's an option to configure chat backoff, but it'd be best to just include a backoff function that spaces out chat messages just right.

While the documentation claims they resolve with a Room instance.

it's probably OK for getRoomState() to do this, but join() should resolve with a Room instance in v2.

documentation should be updated for v1.x regardless.

List from plug-socket:

• ack
• advance
• ban
• banIP
• chat
• chatDelete
• djListCycle
• djListLocked
• djListUpdate
• earn
• sub
• cash
• gift
• floodChat
• floodAPI
• friendRequest
• friendAccept
• gifted
• grab
• killSession
• modBan
• modAddDJ
• modRemoveDJ
• modMoveDJ
• modMute
• modSkip
• modStaff
• nameChanged
• nameChangedRoom
• notify
• playlistCycle
• plugMaintenance
• plugMaintenanceAlert
• plugMessage
• plugUpdate
• rateLimit
• roomNameUpdate
• roomDescriptionUpdate
• roomWelcomeUpdate
• roomMinChatLevelUpdate
• skip
• userJoin
• userLeave
• userUpdate
• vote

I need to get the body of the error when mp.addDJ fails, to parse the error message returned.

Example:

{
    "data": ["This request was understood but is forbidden."],
    "meta": {},
    "status": "noValidPlaylist",
    "time": 12.279033660888672
}

But there doesn't seem to be any way to get it through Promise.catch or the second Promise.then parameter. All I get is the native HTTP Error which isn't very useful.

Sorry if I missed a very obvious way of doing this.

When the waitlist is empty and the last song is finish (or skip) :

  waitlist.forEach((id) => {
          ^

TypeError: Cannot read property 'forEach' of undefined
    at wrapWaitlist (c:\Users\Maxime\node_modules\miniplug\index.js:399:11)
    at EventEmitter.ROLE.NONE [as wrapWaitlist] (c:\Users\Maxime\node_modules\miniplug\index.js:72:12)
    at onDjListUpdate (c:\Users\Maxime\node_modules\miniplug\index.js:855:32)
    at WebSocket.onAdvance (c:\Users\Maxime\node_modules\miniplug\index.js:860:7)
    at emitTwo (events.js:111:20)
    at WebSocket.emit (events.js:191:7)
    at c:\Users\Maxime\node_modules\plug-socket\index.js:24:10
    at Array.forEach (native)
    at WebSocket.onmessage (c:\Users\Maxime\node_modules\plug-socket\index.js:21:13)
    at WebSocket.onMessage (c:\Users\Maxime\node_modules\plug-socket\node_modules\ws\lib\EventTarget.js:103:16)
    at emitTwo (events.js:106:13)
    at WebSocket.emit (events.js:191:7)
    at Receiver.EventEmitter.setSocket.head._receiver.onmessage (c:\Users\Maxime\node_modules\plug-socket\node_modules\ws\lib\WebSocket.js:146:54)
    at Receiver.dataMessage (c:\Users\Maxime\node_modules\plug-socket\node_modules\ws\lib\Receiver.js:389:14)
    at Receiver.getData (c:\Users\Maxime\node_modules\plug-socket\node_modules\ws\lib\Receiver.js:330:12)
    at Receiver.startLoop (c:\Users\Maxime\node_modules\plug-socket\node_modules\ws\lib\Receiver.js:165:16)

My .js

const mp = miniplug({
    email: require('./bordel/auth.json').email,
    password: require('./bordel/auth.json').password
})
// Join a room 
mp.join('la-room-francaise').then((room) => {
    mp.chat(mp.me().username+' Online !');
})```