Roblox Package Manager v0.4.0-beta [UPDATED]

rpm Roblox Package Manager (RPM)

Marketplace | GitHub

Let’s talk about packages

The idea of packages / modules / libraries is to reuse and share code, right? Currently I find this process quite cumbersome, particularly when trying to use tools / plugins within Roblox Studio only. However, if you do some digging you are likely to come across Wally.

For those who don’t know, Wally is a package index & package management tool that is primarily used for a Rojo style workflow (i.e. using a separate editor such as VSCode and syncing changes into studio). There’s a growing number of packages becoming available via Wally, such as . Naturally there is a barrier to using Wally if you stick solely to using Studio.

Enter the RPM plugin. This allows you to search the full Wally package index from studio, and to download specific packages into studio directly.


You can install the plugin straight from the creator marketplace.

Alternatively you can clone the repo, build the plugin using rojo build and move to your local plugins folder.

Windows + PowerShell

For quickly building and re-installing the plugin locally this command has proved useful:

rojo build --output dist/RPM.rbxmx; copy -Force .\dist\RPM.rbxmx $ENV:LOCALAPPDATA\Roblox\Plugins\

Note: this will overwrite the existing plugin in your local plugins folder.


There are currently two menus that exist. One headed with “Download”, the other with “Search Wally”.

If you know what package you want then you can use the download menu by simply entering the package in <scope>/<name>@<version> format e.g. evaera/promise@4.0.0 . When you click download, the package will be downloaded and installed into the PackageLocation in the config (currently set to the default of ReplicatedStorage/Packages).

The search menu is for finding specific packages on the Wally index. You can enter any search term and see results (if there are any). Each result is seperated by scope/name and each result can be clicked to reveal the available versions of that package. A typical use case is searching by a creator / scope and seeing what packages they have.


I am keen to hear all opinions regarding your own package experiences so far. Particularly how you expect to be able to find / refer to dependencies.

I have an idea about using ObjectValues as references to try and create some kind of standard as an alternative to assuming packages like at a certain location e.g. ReplicatedStorage/Packages.

Existing work

In order to create the most useful tool possible it is important to understand the existing infrastrucure & standards that are being used.

  • StudioCLI provides a package manager that allows you to install from the Roblox market place either by name using it’s own package index or via asset id. This is all done through a command line that the plugin provides.

  • Why you should use Wally

  • Rojo & rbx-dom provide a widely used standard for converting between a standard file system layout and Roblox instances.

There have been some other attempts at creating a plugin of a similar nature before. There doesn’t seem to be much current activity for them now.


  • Install from local zip file (e.g. from a downloaded source .zip file from github) :green_square:

  • More package sources e.g. GitHub repos and Roblox marketplace

  • Resolving dependencies :orange_square:

  • Updating currently installed packages / inform if an update is available

  • Uploading packages to Wally from Studio

  • Developing a standard dependency import style

  • Authentication checks for package installs (checksum/hash/public-private key signatures etc.)


Release v0.2.0

New Features

  • Dependency resolution at a depth of one
  • Installed packages are selected in explorer
  • Settings menu to view package install location


I’ll be using this today, and I appreciate you sharing it because it will be very helpful.

It is very beneficial for me and others.
I hope more people become aware of your plugin.

1 Like

Do let me know what you think and what features should take priority. My current thoughts are on the settings menu for choosing where packages are installed.

It is still very much a work in progress which is hopefully reflected by the fact it is still pre v1.0.0

Release v0.3.0

New Features

  • Recursive dependency installation
  • Install from local zip package using the “Browse files” button
  • New logging / output system

Bug fixes

  • Per place config now saves correctly

hey thanks for this plugin this is what i was looking for!

1 Like

Release v0.4.0-beta

New Features

  • UI updates. Text buttons replaced with icons that have hover information


  • Pugin now no longer automatically creates package folders when you open a fresh place. It now waits until you actually install a package.

Bug fixes

  • Zip archive installation now works for more file structures