Skip to content

General

General

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

6 results found

  1. Add better debugging information into Firebase CLI (Python) version. The CLI frequently throws the following error but does not provide any further information, even in debug mode.

    Failed to call quitquitquit. This often means the server failed to start request to http://127.0.0.1:8081/__/quitquitquit failed, reason: connect ECONNREFUSED 127.0.0.1:8081 {"message":"request to http://127.0.0.1:8081/__/quitquitquit failed, reason: connect ECONNREFUSED 127.0.0.1:8081","type":"system","errno":"ECONNREFUSED","code":"ECONNREFUSED"}

    or

    Error: User code failed to load. Cannot determine backend specification

    Details of the error can however be found in the GCP Console and Cloud Build. The same error messages should appear in the CLI as the Console is not a scalable way to maintain/deploy…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firebase CLI  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Firebase functions does not support monorepo structures (NPM monorepo, NX, Turborepo) during deployment.

    Firebase uses custom archive logic for functions packaging (https://github.com/firebase/firebase-tools/blob/127ca3fbf7549d6c0cdf12e89e4465de9dd2b7c9/src/deploy/functions/prepareFunctionsUpload.ts), which does not support internal packages deployment out of the box.

    Github discussion: https://github.com/firebase/firebase-tools/issues/653

    18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Allow deployment from CLI of specific extensions, to avoid uploading and updating all extensions unnecessarily.

    i.e. firebase deploy --only extensions:<name of extension>

    Just like we can with functions.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Firebase CLI  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Similar to the way we can define an index in firestore with firestore.indexes.json. I'm proposing a firestore.ttl.json where the TTL properties would be deployed upon firebase deploy, instead of having to go in the console UI or alternative methods.

    Those configuration files are useful when switching environment as this minimize the configuration required when going from dev, to staging, to prod. Centralizing those in one place makes it easier.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firebase CLI  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. in a svelte-kit app if you have multiple environments (staging, production) you can specify multiple .env files.

    Unfortunately, there is no way to tell Firebase which one to use so it always deploys using production. and always uses development in the emulator

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. I'm currently learning Firebase and want to have a sandbox with the emulators without creating a project on the website every time I want to make another. Currently Firebase Storage does not work without setting a GCP resource location and the only way to set it is via the web console. If there was a way to set it locally via the CLI or a config file that would make it a lot easier to experiment with Firebase.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firebase CLI  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?