63 results found
-
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 -
On Document Update Firebase Function on specfic field update
OnDocumentUpdate firebase function should allow a filter such that function gets triggered when particular field(s) of the document changes. Currently the functions are triggered for every change made to the document. This leads to unnecessary billing.
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?
We need to have something like:
exports.someScheduledFunction = onSchedule(
{
schedule: "every 60 minutes",
timeoutSeconds: 100,
secrets: [someToken.name],
},
async () => {
logInfo("Running every 60 min");...
}
);3 votes -
Cloud Functions versioning
It will be great to have an easy way to deploy different versions of our API and access them by adding a "v1" or "v2" to the URL.
Currently, we can do it manually by changing the name of the function, but the ideal is to have a new parameter in the deployment process (CLI) to "group" them in versions.
This idea is great to roll out and have different versions living side by side until the production version that uses the new API is released to all the users.5 votes -
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.
4 votes -
Make Firebase Functions Test a First Grade citizen
A solid Firebase Functions experience requires a fully functional test suite.
Firebase-functions-test is already there, and provides the experience, but is often forgotten for months.Firebase functions 6 was released a month ago, and it broke functions-test.
There's currently a patch that fixes it, and it's been there for a week.
This idea isn't about this issue. It's about giving resources to the firebase-functions-text project, so it can continue growing and thus giving cloud firebase functions users a solid testing experience before deploying.
4 votes -
Rolex Enterprises
Chair service
3 votes -
not upgrading blaze plan
firebase is not updateing to blaze plan i already have an verified billing account you should have to give more information about how to setup properly
4 votes -
72 votes
-
Create a context.auth (1st Gen) equivalent for 2nd Gen cloud function
1st gen cloud functions can access auth info via context.auth as described here: https://firebase.google.com/docs/database/extend-with-functions?gen=1st#accessing_user_authentication_information
But 2nd gen cloud functions is yet to have the same function.
43 votes -
Increase request size over 32Mb
Right now, a Firebase function can only accept a request payload size up to 32Mb.
Using it as webhook for some external APIs, we would need to have no limits or at least 100Mb limit5 votes -
Fee/Pricing
Functions is behind paywall, (it is still free for some limit in Blaze plan), but IF i upgrade to Blaze, then Cloud Storage, Hosting etc starts to charge right away, even in free plan they have free limits but once switched to Blaze it starts to charge. So to get free Functions, i have to pay cloud storage and hosting and more.
For any playground project that is not gonna hit market or earn money, how i am supposed to try/learn functions? This forces me to move away from platform
8 votes -
Should add basic REDIS/ Memcache Like Capability
Why I Want This?
Firebase splits functions to individual Docker Container. This works great for scaling, but with that it is not easy to share global values, for example, user's access key to external services and session specific values.
While we can use REDIS and such hosted on GCP, it would be more "batteries included" platform if this feature is offered as a built-in functionality for the functions without resorting to Firestore or RTDB.
What I look for is to globally share key values and also auto-expire them.
2 votes -
Sub Collection View
I feel the window to view sub collection on the firebase firestore console could be expandable.
2 votes -
It is necessary to change and update in advance the spread of better ideas that benefit people and reduce harmful materials
It is necessary to change and update in advance the spread of better ideas that benefit people and reduce harmful materials
2 votes -
Add an argument that automatically chunks cloud function deployments according to the maximal possible quota
When deploying multiple cloud functions at once via
firebase deploy --only functions
we frequently run into quota issues like:
functions: got "Quota Exceeded" error while trying to update projects/.... Waiting to retry...
It never retries though.
It would make it way easier if you could add an argument to the deployment command like:
firebase deploy --only functions --chunked 50
4 votes -
Flutterflow despliegues correctos
muchas veces flutterflow no permite desplegar cloudFuctions y es muy importante el poder crear cloudFuctions desde flutterflow
3 votes -
Tell people that mixing V1 and V2 config files in the same project will create a port and container error.
Tell people that mixing V1 and V2 config files in the same project (note: even outside the gen2 function) will create a port and container error. Right now you don't mention in the docs or anywhere that having ANY function.config files in a project with a gen 2 function will cause a deploy error that says a container is broken and the port is unreachable. This error is misleading. It will also show the gen 2 function in the console as "unknown trigger" which also is misleading.
In all your documentation you say you can have gen1 and gen2 functions…
2 votes -
Support Go in Cloud Functions
Go is much more efficient than Python or Js and should be the obvious choice for backend where performance is crucial
34 votes -
Support TypeScript in Cloud Functions
It's a pain to have to configure a process to watch and transpile TypeScript files to use in the emulator. Firebase CLI should have built-in support for it both in the emulator (with automatic watching, or on-the-fly transpilation as I showed here https://github.com/firebase/firebase-tools/issues/5633#issuecomment-1622585432) and when deploying.
30 votes
- Don't see your idea?