You should have put it in a .rbxm file, not a .rbxl. I now have to open a new place just to view the module.
I’d advise developers that are not using Rojo (especially new developers), to stay away from frameworks. They prevent intellisense from working, and you have to write boilerplate code in every single module: they’re just not worth the burden. Instead new developers should use plain module scripts, that’ll be better in the long run.
This is just a Module Loader… the modules that are installed in Nuclear currently can just be single handedly used in game without this loader. So I guess what I am trying to say is why use this?
This could be something useful if it had some batteries in it, if you get me, (Features it has by default), the main reason people choose Knit and other frameworks is because they have some things integrated by default which makes some stuff easier, this lacks that
At the moment, this is still up for debate, and there isn’t a definitive answer on whether Rojo is objective better for everyone, or not. But the general advise is to use what you’re more familiar with. New developers who haven’t programmed in another language would be better off using Roblox Studio over Rojo.
And even in Rojo, frameworks like Knit is not recommended by the creator of Knit, because you lose out on intellisense (and other reasons too mentioned in the article), unlike just using a Module Loader. Unless you have a workaround, just use a simple module loader, or just modules