Shared Backend Logic in a non-public directory next to /functions and /src
The Problem
Building robust apps with multiple backend functions often requires shared logic β validation, calculations, transformations. Right now, Base44 forces you to either:
Duplicate code across functions (maintenance nightmare, bugs multiply)
Call functions via HTTP internally (extra latency, brittle architecture)
Neither is acceptable for production-grade apps.
What we need
A dedicated
/shareddirectory (or similar) that:
Can be imported by any backend function via relative import
Is not exposed as an HTTP endpoint
Is treated by the AI as a central, reusable module β not something to be inlined or duplicated
Why this matters
The AI currently "thinks locally" β every time it touches a function, it rebuilds logic from scratch instead of recognizing and reusing shared modules. A first-class
/shareddirectory would give the AI a clear architectural signal: THIS code is shared, reference it, don't duplicate it !!!
This isn't just a developer convenience. It's the difference between apps that scale and apps that break the moment you need to update a single piece of logic in five places.
The ask
Make Base44 the platform where serious apps are built seriously. Give us
/sharedπ
Please authenticate to join the conversation.
In Review
Feature Request
About 3 hours ago

nilei
Get notified by email when there are changes.
In Review
Feature Request
About 3 hours ago

nilei
Get notified by email when there are changes.