Recommendation

[xhayper]

• Transport and Scopes should not be customizable, it should be hard coded, ipc transport with rpc scope.
• Consider switching to my discord-rpc library as discord-rpc is really outdated.
• Consider using undici instead of node-fetch
• Add private field to package.json so it can't be publish accidentally.

[fisherjacobc]

👋 Hi there! I have seen your suggestions and have some comments for them

• Im not sure how to make the scopes hardcoded considering i dont think they are ever mentioned anywhere, but I could make the transport hard coded
• I am interested in knowing what advantages yours has compared to the older one, as the older one seems to work just fine
• I'm not planning on switching from node-fetch, even tho it is pretty bad because I just make one simple request and dont need a wide range of features
• I have added that private field as you suggested

[xhayper]

You actually don't need any scope at all, it just work out of the box (both mine and older one).

[xhayper]

also my discord rpc provides a much better development experience as the error points out to the correct place, and it comes with typing out of the box.

My version also supports snap store and flatpak out of the box (if you don't know, studio can be run via wine now (linux))

[xhayper]

Another thing, transport should be hardcoded to ipc as websocket never work

[fisherjacobc]

You actually don't need any scope at all, it just work out of the box (both mine and older one).

I dont see much advantage to switch now as the default one works out of box, considering you switch it to IPC

also my discord rpc provides a much better development experience as the error points out to the correct place, and it comes with typing out of the box.

Not sure what you mean about the errors, and since this isnt typescript (which i prefer, but make it easier with just js for learners) it doesnt come with many advantages

My version also supports snap store and flatpak out of the box (if you don't know, studio can be run via wine now (linux))

I don't understand how this is related because the studio plugin sends http requests so I don't think its effected by platform unrelated by glad to hear you can run studio with wine!

Another thing, transport should be hardcoded to ipc as websocket never work

Yes, I know that websocket doesnt work

[xhayper]

I don't understand how this is related because the studio plugin sends http requests so I don't think its effected by platform

The way the rpc lib connect to discord is by using path, and since discord-rpc doesn't handle flatpak or snapstore version of discord's path correctly, it means that flatpak / snapstore version of discord won't work on discord-rpc, that is the reason why i bring up wine, since some linux user use roblox studio and using flatpak / snapstore version of discord won't have the rpc. there's a workaround for this but it require the user to do a symlink