Tom Jardine-McNamara

Wonderful, thanks!

I've just encountered this too. `NODE_ENV` is undefined (as @codecontemplator pointed out) by default. When I run node from the cli, that's the case: ``` bash $ node > process.env.NODE_ENV...

The firestore emulator runs at `http://localhost:8080`, so try: ``` const test = require('firebase-functions-test')({ databaseURL: 'http://localhost:8080', storageBucket: 'my-project.appspot.com', // Emulator doesn't support storage yet projectId: 'my-project', }, 'path/to/serviceAccountKey.json'); ``` And then...

> @itsravenous Did you ever manage to figure this out? Running into the same problem. Nope, I ended up writing integration tests instead, using `firebase-admin` to write data to firestore...

As requested in #8

@ziw would love to know if you ever figured this out. I'm writing e2e tests and have tried both `overrideProviders`: ```ts const moduleFixture: TestingModule = await Test.createTestingModule({ imports: [AppModule], })...

This issue appears to be present in latest release - I can set breakpoints but they are never hit. I'm using the example here https://github.com/milankinen/livereactload/tree/master/examples/03-build-systems UPDATE: Breakpoints are hit in...

@milankinen thanks for the swift response! I saw the rev= issue initially, but it goes away after first refresh (yep, super weird I know) and Chrome shows my breakpoints persisting...

Wait, I lied :D Yes, when I make an edit to a component, a `rev=` is added, so yes, Chrome sees it as a different file. But that's a separate...

If I add a `debugger` statement in my code, Chrome pauses on that, and any subsequent breakpoints are also hit. So I can work around this for now when I...