As a Roblox developer, it’s always been hard to use the PlayerModule. Since it’s not actually present in the DataModel in edit mode, it has no autocompletion or API available to read when scripting. This is very bad developer experience (DX)! You’re forced to fork it even if you only want to use it, not change it. And when you fork it, it may break over time or become outdated.
This DX issue could be fixed if the PlayerModule was a Roblox-owned package that can be set to auto-update. You can do diff checks when an update happens, making integration a lot easier. And for bonus points, upload and maintain it on wally! That’d make a lot of Rojo users happy.
I feel like this is moreso an issue touching on the need for a formal package manager. I would imagine this would be supported at some point especially based on recent updates.
What features would you like to see in a native package manager? I’d like to be able to make changes and be able to “keep” those changes in newer versions when the creator updates it. That’d help everybody who immediately after forking the PlayerModule, would edit the CameraModule to actually return the cameras and not an empty table.
There’s probably Git terminology that describes this but I’m Git illiterate so I wouldn’t know.
