Firebase emulators:start --only hosting:<target> is not working #2103

ChromeQ · 2020-04-06T10:50:34Z

[REQUIRED] Environment info

firebase-tools: 7.11.0

Platform: Ubuntu 19.10

[REQUIRED] Test case

npx firebase emulators:start --only hosting:staging
i  emulators: Starting emulators: 
⚠  Not starting the hosting:staging emulator, make sure you have run firebase init.
✔  All emulators started, it is now safe to connect.

[REQUIRED] Steps to reproduce

Here is a sample firebase.json and .firebaserc files to show targets are set up:

// .firebaserc
{
  "projects": {
    "default": "test-project-dev",
    "staging": "test-project-dev",
    "prod": "test-project-prod"
  },
  "targets": {
    "test-project-dev": {
      "hosting": {
        "staging": [
          "test-project-dev"
        ]
      }
    },
    "test-project-prod": {
      "hosting": {
        "prod": [
          "test-project-prod"
        ]
      }
    }
  }
}

// firebase.json
{
    "emulators": {
      "firestore": {
        "port": 5002
      },
      "functions": {
        "port": 5001
      },
      "hosting": {
        "port": 5000
      }
    },
    "hosting": [
      {
        "target": "staging",
        "public": "build",
        "ignore": [
          "firebase.json",
          "**/.*",
          "**/node_modules/**"
        ],
        "headers": [ ... ],
        "redirects": [ ... ],
        "rewrites": [ ... ]
      },
      {
        "target": "prod",
        "public": "build",
        "ignore": [
          "firebase.json",
          "**/.*",
          "**/node_modules/**"
        ],
        "headers": [ ... ],
        "rewrites": [ ... ]
      }
    ]
}

Below is the output of other firebase commands to show the targets are set up correctly:

npx firebase target
Resource targets for test-project-dev:

[ hosting ]
staging (test-project-dev)

npx firebase use prod
Now using alias prod (test-project-prod)
npx firebase target
Resource targets for test-project-prod:

[ hosting ]
prod (test-project-prod)

When running npx firebase emulators:start --only hosting without a target then it starts both targets successfully. I'm trying to get it to run with just one at a time.

npx firebase emulators:start --only hosting
i  emulators: Starting emulators: hosting
i  hosting[staging]: Serving hosting files from: build
✔  hosting[staging]: Local server: http://localhost:5000
i  hosting[prod]: Serving hosting files from: build
✔  hosting[prod]: Local server: http://localhost:5005
✔  hosting: Emulator started at http://localhost:5000
✔  All emulators started, it is now safe to connect.

[REQUIRED] Expected behavior

I would expect this to start the emulator with only the target specified. But it closes the emulators immediately

[REQUIRED] Actual behavior

The text was updated successfully, but these errors were encountered:

google-oss-bot · 2020-04-06T10:50:36Z

This issue does not have all the information required by the template. Looks like you forgot to fill out some sections. Please update the issue with more information.

samtstern · 2020-04-06T12:05:22Z

@ChromeQ thanks! This seems like a straightforward bug. For now your best workaround is to use firebase serve for advanced Hosting commands like this one.

adam-remotesocial · 2020-10-16T21:38:31Z

Hi there! I'm running into this bug now and just wanted to detail an issue with the workaround.

I've tried to work around it by:

starting the other emulators with firebase emulators:start --only database,firestore,functions
starting hosting for just the target I want with firebase serve --only hosting:target
When I initializeApp() I then update functions and firestore to point to emulators:

    firebase.functions().useFunctionsEmulator('http://localhost:5001');
    firebase.firestore().settings({
        host: 'localhost:8080',
        ssl: false,
    });

But there is no way I've found to alter the databaseURL after hosting has already set the options in initializeApp(), and hosting doesn't know about the RTDB emulator.

Next experiment is using a firestoreConfig globbal variable that I'm not sure where it came from and explicitly changing the databaseURL in initializeApp without changing any other config. Hopefully that works. I do wish the bug would be fixed though. This has made my dev setup extra complex with the separate shell commands I have to run together.

Cheers!

adam-remotesocial · 2020-10-18T22:40:47Z

^ ok fresh mind now and I'm realizing that calling initializeApp with firebaseConfig is not possible because the initializeApp call happens inside of init.js which is controlled and served by the hosting emulator and/or firebase serve. So either I'm missing something (very likely!) or it seems there's no workaround for this bug unless I start proxying the init.js file and transforming it which feels kinda terrible.

EDIT: Another option is generating a custom config that only has the target I want and then firebase --config ./.generated/config.json emulators:start, even if I cry a little inside at the thought.

samtstern · 2020-10-19T11:25:33Z

@adam-remotesocial this is a huge pain and we're working on it as we speak:
firebase/firebase-js-sdk#3904

Once that PR is merged and released (a few weeks, probably) you'll be able to call firebase.database().useEmulator('locahost', 8080) after initializeApp() as long as you haven't yet used the database to access any data.

And then once that is all in place we'll be able to modify the magic __init.js file to use those APIs for you, so it's even more magic :-)

adam-remotesocial · 2020-10-19T22:31:00Z

Oh wow that's great. Thank you!

ChromeQ · 2021-03-02T14:47:30Z

@ChromeQ thanks! This seems like a straightforward bug. For now your best workaround is to use firebase serve for advanced Hosting commands like this one.

Hi @samtstern, now that the other issues raised are fixed and merged in firebase/firebase-js-sdk#3904, is this original issue still a "straightforward bug"? Been running into this issue again when trying to emulate and debug an issue in prod vs staging targets as outlined in the desc.

Thanks

samtstern · 2021-03-03T12:09:40Z

@ChromeQ yes I would still consider this a bug, we did add the magic __init.js stuff but I think emulators:start still has issues with multiple Hosting targets.

ChromeQ · 2021-03-15T06:14:54Z

I see v9.6.0 mentions

Fixes issue where the Firebase Hosting emulator would fail to start with --only filters using targets (#2820).

It sounds like the bug raised in this issue, and I've updated to the latest version and it seems to be fixed 🎉
I think I can close this issue now

samtstern added emulator-suite emulators: hosting type: bug labels Apr 6, 2020

ChromeQ closed this as completed Mar 15, 2021

snyk-bot mentioned this issue Jan 16, 2022

[Snyk] Upgrade yargs from 13.3.0 to 17.3.1 majacQ/firebase-tools#19

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Firebase emulators:start --only hosting:<target> is not working #2103

Firebase emulators:start --only hosting:<target> is not working #2103

ChromeQ commented Apr 6, 2020

google-oss-bot commented Apr 6, 2020

samtstern commented Apr 6, 2020

adam-remotesocial commented Oct 16, 2020

adam-remotesocial commented Oct 18, 2020 •

edited

samtstern commented Oct 19, 2020

adam-remotesocial commented Oct 19, 2020

ChromeQ commented Mar 2, 2021

samtstern commented Mar 3, 2021

ChromeQ commented Mar 15, 2021

Firebase emulators:start --only hosting:<target> is not working #2103

Firebase emulators:start --only hosting:<target> is not working #2103

Comments

ChromeQ commented Apr 6, 2020

[REQUIRED] Environment info

[REQUIRED] Test case

[REQUIRED] Steps to reproduce

[REQUIRED] Expected behavior

[REQUIRED] Actual behavior

google-oss-bot commented Apr 6, 2020

samtstern commented Apr 6, 2020

adam-remotesocial commented Oct 16, 2020

adam-remotesocial commented Oct 18, 2020 • edited

samtstern commented Oct 19, 2020

adam-remotesocial commented Oct 19, 2020

ChromeQ commented Mar 2, 2021

samtstern commented Mar 3, 2021

ChromeQ commented Mar 15, 2021

adam-remotesocial commented Oct 18, 2020 •

edited