Author thinks breaking the package on purpose is not an issue about rpc HOT 4 CLOSED

I'll suggest you something, cd /node_modules/discord-rpc && npm i discordjs/discord.js#your-desired-commit-hash.

Problem solved, and please don't open the same issue multiple times.

from rpc.

To be honest, what I do in some repositories is make discord.js a peer dependency, so people install their desired version/commit hash, although the support becomes more tricky because it's very hard to enforce support in a library that is quickly changing.

Nonetheless, when discord-rpc becomes stable, it'll most likely use a stable version of discord.js, being either v12.0.0 (whenever it releases as stable) or locked to a commit. This library is currently beta, so you shouldn't expect full stability.

from rpc.

But this just workaround, I think this issue should be fix

from rpc.

I actually pin them to master because rpc will become stable with v12 and pinning to a hash will backtrack compat. I appreciate that you think I don't care but in actuality I'm just being pragmatic.

from rpc.