Framework RageFW - RAGE:MP server development kit

[Uristri]

What is already implemented:

•     Universal communication: RageFW makes it easy to call events and receive responses between all server components (server, client, cef). No more need to manually throw additional events!
•     Full type-safety: Code becomes more reliable and easier to maintain due to strict type-safety.
•     User-friendly CLI: Quickly create new projects and start development without unnecessary customizations.
   

Documentation:

•     Full documentation: Link*
•     CLI: Link*
•     Library: Link*

Important:

RageFW is in an early stage of development and may contain bugs. We would very much welcome your feedback, suggestions and participation in testing. Together we will make development on Rage:MP even easier and more enjoyable!

Edited June 15, 2024 by Uristri
links not working

[Kopra]

I like the simplifying and abstracting stuff for newer users. Sounds like an interesting boilerplate start for now. Will follow!

[Uristri]

Good afternoon everyone, the lull is over (hopefully) and we're back with lots of news and updates

Since most probably aren't aware of it and the topic has been lying dead for a while now, Rage FW is a collection of various tools to make it easier to write Typescript servers for Rage:MP.

Until recently, it included four libraries for writing server-side, client-side, and browser-side code, as well as a common library that distributes types across all environments; in addition to which came a CLI for quickly deploying such a project and a Rage:MP server file loader.

Now let's talk about what has changed

CLI
Added a new template for the frontend - Svelte 5. Also added an option to deploy a project with a basic demo of using self-descriptive RPC (about which next). Read and poke here

RPC
Due to the lack of ability to type events in the much-loved rage-rpc and personal interest, it was decided to write a custom (which is now also used in the core libraries) RPC with desirable functionality and new, highly desired by developers, features.

Additionally, it includes a built-in (optional) event logger, a more extensive and detailed error handler, and the ability to run frontend code in dev-mode from a browser, out of mp context with just one setting, without the lovely mp is not defined error and white screen.

You can explore in more detail here (or here), poke around here, help with development there

Core (Server/Client/Browser)
In addition to moving to self-describing RPC, which made the code even more secure and easier to read in terms of types, new functionality was also added:

• added midllewares for Server and Client events. These can be hung at the moment of event registration to check incoming data and potentially cancel the callback if needed
• Along with the move to the new RPC, the browser also has the ability to run the frontend in dev-mode outside of mp context (described earlier).

And edits/additions:

• improved and, in some places, corrected function typing
• type names now follow a common pattern and order
• code is now abundantly described by JSDoc for quick access to explanations and function examples.

Github
Follow updates here

Adequate criticism and interesting ideas are extremely welcome. Thanks for your attention

Edited November 2, 2024 by Uristri