62 results found
-
Automatic Deployment of Changed Firebase Functions
Firebase should offer a built-in feature to automatically detect changes to Cloud Functions and deploy only those functions, grouped into manageable batches to avoid rate limits. This feature would streamline deployments by:
- Scanning the project directory to identify functions with modified code since the last deployment.
- Automatically batching the deployment of changed functions based on rate limit thresholds (e.g., 8-10 functions per batch).
- Handling the deployment process transparently within the Firebase CLI or CI/CD integrations, reducing manual intervention.
This functionality would save time, minimize deployment errors, and improve developer workflows, particularly in large projects with numerous functions.
38 votes -
A
Bahut fir bes hi chalan asan hi
1 vote -
Support Dart in Cloud Functions
Dart is not currently supported in Cloud Functions, so developers need to use more than one language in their code base. Here are some pain points they shared with the Firebase product team about this gap:
- They need to learn another language, and many of them do not have the same expertise in JavaScript as they do in Dart.
- The lack of features and tools, such as Hot Reload and Hot Restart, impacts development speed.
- Developers cannot share business logic and data models across the entire stack.
- Developers cannot use frequently used Dart packages on the…842 votes -
Infinite loop/recursion detection
It's possible to make a mistake that causes a function to trigger itself (for example, an onDocumentWritten Firestore trigger that writes to the same document). If Cloud Functions for Firebase could detect this and shut down the infinite loop, it could prevent runaway bills.
It could also be a feature in the emulator suite so that we could check for them before deploying to production.
2 votes -
افكار ساخنه
كل انواع النشاط واحدث الميزات انفنكس اصدار الحدث
1 vote -
🚀 Advanced Proposal: Hybrid Firebase Architecture for Optimized Performance, Offline Access & Cloud Resilience
🧠 Core Strategy
Deploy Firebase Studio locally (on-premise or VM)
Integrate with Firebase Emulator Suite + Edge Cache
Enable automatic sync with Firebase Cloud
Allow direct access to local services (filesystem, DB, devices)
Use secure reverse tunnels and proxy APIs for controlled cloud interactions
✅ Key Benefits Overview
Feature Benefit
✅ Offline First Use Firebase Emulator Suite to run Firestore, Auth, Hosting, Functions entirely offline
✅ Faster Performance Local queries eliminate latency from cloud round-trips
✅ Access Local Resources Direct access to local files, OS services, SQLite, or PostgreSQL
✅ Data Control Comply with GDPR/PDPA by keeping sensitive data local…2 votes -
Add Support for Aggregation Functions and Regex Filtering in Firebase Realtime Database
Firebase Realtime Database currently lacks support for aggregation functions (like sum, count, average) and regex-based data filtering. These features would simplify querying, reduce client-side processing, and improve performance, especially with large datasets. While Firestore offers some of these capabilities, Realtime Database remains the preferred choice for real-time syncing. Native support for these functionalities would greatly enhance its potential and usability.
6 votes -
Auth onUpdate trigger for v1 and v2 functions
In the same way, we have onCreate and onDelete, it will be very helpful to have an onUpdate option. For example, so we can react to an email address change.
54 votes -
Support Direct VPC
A static IP is a must-have feature when dealing with certain services.
In the past, we could use Serverless VPC Access connectors, but this required renting a virtual machine (VM), which contradicts the principles of serverless architecture and significantly increases costs.
Recently, a new method called Direct VPC has emerged, which eliminates the need for connectors. This means it is truly serverless, even when using a static IP.
Currently, Direct VPC can be configured by revision in the Google Cloud Console. However, I would like to enable Direct VPC in Firebase Functions as an option, like so:
vpcConnector: 'test-connector',
vpcConnectorEgressSettings:3 votes -
Support Swift in Cloud Functions
Swift is a much beloved and popular language for writing apps on the Apple platforms, but increasingly, it is also being used server side and even for writing cross platform business logic on Android and on Windows.
Being able to share models and business logic between your clients and server would be an amazing productivity boost. And being able to develop in a language that focuses on safety would eliminate categories of issues that can exist if you develop in say Javascript or Typescript.
333 votes -
Consistent and documented behavior for on*WithAuthContext
When Functions use e.g. onDocumentCreatedWithAuthContext to handle Firestore event triggers, the meaning of event.authType and event.authId are not documented and are inconsistent between the production and emulator environments.
The documentation [https://firebase.google.com/docs/functions/firestore-events?gen=2nd#auth-context](here) says "For information about the data available in the authentication context, see..." and links to a page that is not specific to Firebase. That page lists some possible values, but it's not clear what values would be used. The most sensible guess is that authType would be "appuser" or "user" if the document was created from the client-side web SDK, and "serviceaccount" if created from a…
3 votes -
Improve Billing Verification and Support for New Firebase Users
Many new Firebase users face serious issues when trying to activate the Blaze plan due to strict and non-transparent billing verification processes.
In my case:
• I attempted to verify my billing using a Revolut card (registered under my name);
• All payment confirmations were approved through the Revolut mobile app (4–5 times), yet the verification still failed;
• No clear error explanation was provided, and I had no way to resolve the issue;
• I tried adding a backup Korean card, but the verification message never arrived in the Korean mobile banking app (SMS also didn’t arrive because my…3 votes -
Fix error messages when deploying Functions
Several error messages often occur when deploying Firebase Cloud Functions that should not occur. My first time attempting to deploy functions in a new project, I got:
i extensions: ensuring required API firebaseextensions.googleapis.com is enabled...
⚠ extensions: missing required API firebaseextensions.googleapis.com. Enabling now...Error: Request to https://serviceusage.googleapis.com/v1/projects/********/services/firebaseextensions.googleapis.com had HTTP Error: 429, Quota exceeded for quota metric 'Default requests' and limit 'Default requests per minute' of service 'serviceusage.googleapis.com' for consumer 'project_number:********'.
I don't know if that happens every time. It appears to be just a failure to wait long enough after enabling the API.
The second time, it got further, but…
3 votes -
Allow ordering functions when they are displayed in firebase console.
As a non-expert user, I am trying to avoid navigating the Google Cloud Console ("GCC") when possible (which should be understandable since that is largely the point of Firebase). So when an internal error in one of my functions occurs, I go to the firebase console, find the relevant function and then select "see logs" which takes me the to the precise place in GCC. The issue is that the function in the Firebase console seem to be displayed in random order with no way of ordering them... so it is always a pain to scan through them to find…
1 vote -
allow secrets on scheduled functions
It's not clear in the documentation nor by implementation that secrets work with scheduled cloud functions. This seems to me like a major missing feature in security and consistency with the v2 cloud functions. Is the only solution using the cloud config for api keys/secrets? Something like:
exports.someScheduledFunction = onSchedule(
{
schedule: "every 60 minutes",
timeoutSeconds: 100,
secrets: [someToken.name],
},
async () => {
logInfo("Running every 60 min");...
}
);6 votes -
Add support for local npm packages
Change the behavior of dpeloy for functions so that if a local (file based) npm package is listed in the package dependencies, the package will be uploaded with the function.
It is a major pain for local packages to not be supported in uploading cloud functions.
4 votes -
new Firebase Authentication trigger
firebase currently has two firebase auth triggers:
functions.auth.user().onCreate()
functions.auth.user().onDelete()I would like a trigger to respond to onLinkWithCredential so that I can update the user document in the user collection with the additional/changes from the new auth method
18 votes -
Support .NET (C#) in Firebase Functions.
Firebase has .NET SDKs for the client and admin SDKS. It would be nice if Firebase Functions supported .NET (C#) especially since GCP Cloud Run Functions already support .NET.
3 votes -
Fix Body Parse
If bad JSON is sent to a cloud function, for example if the function is an API endpoint, the body-parse in Firebase Functions will throw an HTML response error before and user function code is run.
This is a really bad experience for endpoint users where instead of a formatted JSON error message, they get a strange HTML response.
The body-parser used in by Firebase Functions should pass along the error instead of returning the response.
4 votes -
Enable source map support
Since Node 12 it has built-in source map support. For cloud run deployments we can start the node server with the flag --enable-source-maps, but for cloud functions we don't have this control.
I don't understand why we still need to install and register the source-map-support NPM package in our code to get source maps to work.
I suggest to have a configuration option that enables the flag, preventing us from having to manually install a package that is considered obsolete for newer versions of Node.
4 votes
- Don't see your idea?