Skip to content

Releases: thenolle/discord-rpc

v1.0.0 - First stable release

20 May 22:51

Choose a tag to compare

Discord RPC v1.0.0 is the first stable release of the project. It delivers a lightweight Rich Presence app built with Bun, a custom browser-based GUI, tray-based background behavior, and portable single-file builds without heavy framework.

Highlights

  • Bun-based runtime and build pipeline
  • Custom local web UI with Discord IPC support
  • Rich Presence support for timestamps, party data, buttons, streaming, and external images
  • Tray-based background app behavior
  • Portable Windows executable with no terminal window on launch
  • Embedded Windows executable icon and working tray icon
  • Cross-platform build targets for Windows, Windows ARM64, macOS, macOS x64, and Linux

What changed

  • Migrated the project from the older Node-oriented packaging flow to Bun for development and executable builds
  • Converted the app codebase from JavaScript to TypeScript
  • Replaced the previous tray implementation with a cross-platform native tray solution
  • Removed the old hidden VBS launcher approach
  • Added a Windows post-build patch so compiled executables launch without opening a console window
  • Added Windows executable icon embedding during build
  • Simplified the release flow around direct Bun compile targets and post-build helper scripts

Included functionality

  • Connect to Discord through local IPC
  • Edit and apply Rich Presence from the local browser UI
  • Configure details, state, activity type, timestamps, party size, buttons, and streaming URL
  • Use external images through direct URLs and Imgur upload/proxy support
  • Save configuration locally and reopen the UI from the tray at any time

Notes

  • Windows is the primary portable release target for v1.0.0
  • macOS and Linux build targets are available, but platform-specific runtime validation may still vary depending on local system libraries and tray support
  • This release replaces the previous launcher-based Windows startup flow with a cleaner compiled executable path