Loom | Import (Wally) packages or Rojo files natively inside Roblox Studio

Resources Community Resources
,
1

:hammer: Roblox Plugin | :floppy_disk: GitHub Repo

830Ă—310 26.5 KB

Loom, native Wally package manager for Roblox Studio

Loom is a native package manager for Roblox Studio that imports and manages Wally packages directly inside the editor. Loom is a Roblox Plugin which was created for those unfamiliar with Rojo, with its simple injection of packages which follow rojo’s code structure (.client.luau, .server.luau, etc..).

:construction_worker: Plugin Usage / Documentation

Before use, run this inside the Command Box to allow Loom to access HttpService.

game.HttpService.HttpEnabled = true

:balance_scale: License & Holder Agreement

Loom is available under the MPL-2.0 License. Terms and conditions are available in LICENSE.txt or at the Official Website.

With respect of @UpliftGames, and Wally’s License (MPL-2.0 License). I hereby consent to any actions or modifications, including deletion, that they may make toward J4KEWasNotHere/Loom.

Alt text

Click Me!

19 Likes
2

Oh wow JUST 8 DAYS AGO???

Good thing lmao, since I’m using Yeet and it doesn’t support wally directly this is SUPER good to have

1 Like
3

I’m glad you like the idea, I’m still going to need to release an update for it because Wally’s import architecture is very comlicated.

4

The plugin is good, however when I first tried using import from the zip button the whole plugin has lagged broke. Also even though I have HTTPService enabled, it always prints a warning into my output, could that be fixed?

1 Like
5

This is great for when I’m developing with others who don’t use Rojo or Wally. Thank you!

1 Like
6

I’ve also realized this, I’ll recommit as soon as possible; for now you’ll need to turn Developer Mode on and reload the plugin.

Edit: Ok, I just created the patch from .0 to .2 which also covered a few other problems. (V0.2.2)

7

Sounds nice, thanks for the update

1 Like
8

very nice plugin, i suggest supporting .model.json because some packages use those to create instances and those instances end up not being created in studio which breaks the scripts

example: Chrono/src/Shared/Remotes at master · Parihsz/Chrono · GitHub in parihsz/chrono none of the remotes were being made and so absolutely none of the module could function

1 Like
9

Just a quick headsup there is no LICENSE file in the linked repo ( https://github.com/J4KEWasNotHere/Loom/blob/main/LICENSE )

10

Just a quick headsup there is no LICENSE file in the linked repo. ( https://github.com/J4KEWasNotHere/Loom/blob/main/LICENSE ) There is a license txt though (Loom/LICENSE.txt at main · J4KEWasNotHere/Loom · GitHub)

11

That’s pretty interesting. How does it handle package updates?

12

As of right now, it doesn’t. It cant actually be considered a package manager as of right now as it just imports packages. However in future versions I do plan to make it help with update warnings, updating of packages and version control.

2 Likes
13

Noted, I’ve switched to a rojo-build so anyone can submit pull-requests. If your willing to take on the challenge please do! otherwise, I’ll try to get on this now.

14

This seems to have an issue of where it can not fetch a version if there is only one version of something. Could be caused by something else aswell. ( Package I tried to install Wally )

1 Like
15

I’m excited to tell you that .model.json files are now supported with and including property/children support! It will be coming to the future version; once I prepare everything.

Screenshot 2026-07-19 082337
Screenshot 2026-07-19 082337306Ă—376 12.6 KB

Just released v0.3.0!

1 Like
16

Is there a way to export the types from these imported packages?

17

Do you mean versions?ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ

18

hey btw the luau team is working on an offical package manager of the same name, so you should probably change the name of this to avoid future confusion

1 Like
19

I also think renaming it would be a good idea.
loom is already a usable package manager in Lute, so having two package managers with the same name could cause some pretty significant problems.

20

Wow, I didn’t know that!

To be honest, I generated a few names for a “package manager” like Wally, and Loom was one of them, and with AI being so convenient to reference everything it likely picked that up some how.

However, I’d like to see what happens to the plugin after some time and updates. If it does get deleted i’d likely just create a simple spin off of the name like “Loomy”.

I’d likely have to change the repo’s name to explicitly mention its for roblox studio, but that would break alot of functionality, so we need to see how Roblox’s going to react as well as the Luau team.

EDIT: And before you say the logo is ai slop, its not.. I also have it saved as an .svg which I handcrafted myself, and the font i just copied it from using a font scanner..