I know.
However, there are a lot of packages for Roblox on npm with roblox-ts.
These are designed to be transpiled and then inserted into Roblox with Rojo.
The difference with this is that it allows you to insert it directly into Roblox studio, as well as publish directly from Roblox studio. Also, this is a plugin and does not require any additional software.
Sure!
-
local scriptBlankSource = v.Source
line 29 (Internal.encode
) -
local data = require(script.Parent.Parent.Internal.encode)(packageFile)
line 113 (Util.UserInterface
) -
func()
line 60 (Util.UserInterface
)
Alright, Iāve fixed the issue! Turns out I was referencing the wrong instance
Anyhow, the plugin should be fixed now, and you should just need to reload studio now!
Kk! Also, do you want me to help you update the encoder?
That way itāll support comments and extra folders? If so DM me ^āæ^
Alright, should be fixed! Sorry for the issue!
Make sure youāve updated your plugin, I just pushed an update in regards to a new account system! This system allows you to create your very own RPM account, which will allow you to edit RPM packages youāve created.
EDIT: if the issue occurs again, relaunch studio to get the latest module. I forgot to add a slash in the URL.
Alright, Iāll look into it. Thanks for the heads up!
Aight. Also, when I published my packageā¦ It published it as āblaster_202ā instead of Libful? Is that intented?
Not intended, read the PSA posted above. Iām working to get it fixed ASAP.
Looks interesting definitely could be used by people who still use studio.
Does this have any of Robloxās OSS modules, like Roact or Rodux yet?
Every single time I see the title, I am reminded of Redhatās Package Manager (Which is also called RPM)
It does not have Roact or Rodux yet, but I plan to port them soon. Although the porting is not top priority, it is up there on the todo list.
I hate having objects inserted into my game especially if its just for checking a version of something, Do you mind changing the āRPMPluginVersionā that gets loaded into ServerStorage into an attribute instead? Its more out of the way and a bit more hidden.
I will most likely do this, although it is not top-priority, the current version checker is just a placeholder for now.
What exactly is stopping someone from running a command and adding thousands of plugins on your repo with malicious code? I donāt see any authentication here on the POST requests.
Likewise, doing authentication through obscure path names is not a good idea - they can be easily fuzzed and then not only can people upload anything they want, but also delete too.