fmLib

Problem

Any FiveM script that wants a real market has to support ESX, QBCore and QBox. Without an abstraction layer that means three code paths for players, items, money and notifications in every single resource. Triple the surface, triple the bugs, triple the maintenance.

What we built

The abstraction layer we wanted to exist, released as open source:

• One API wrapping the major frameworks, so a script written against fmLib runs on all three unchanged
• Wrappers for commonly used resources on top of the framework layer
• Extra modules for tasks every script needs, on the Lua side and as React-based NUI components on the web side
• Public documentation at docs.rxscripts.xyz/fmlib

It is the foundation under our own commercial catalog, which keeps it maintained and tested in production rather than sitting as a demo repository.

Stack

Lua with React-based web and NUI utilities, published on GitHub under an open license.

Outcome

fmLib has been downloaded more than 23,000 times, carries the multi-framework support for every script we sell and is free for any FiveM developer to build on. Writing that support once, properly, is a large part of why our scripts install in minutes instead of days.