Bryan Kendall

Soooooo here's a fun story: I went diving through the code a bit to see why it would be ignoring `node_modules` and found a [neat line of code](https://github.com/firebase/firebase-tools/blob/78f11b6/src/prepareFunctionsUpload.js#L67). Basically, if...

@shukob if it ends up in your `node_modules` folder, you can use the information in [the comment above](https://github.com/firebase/firebase-tools/issues/968#issuecomment-434766838) (and the one below it) to include your `node_modules` folder.

Hey @antonstefer - As you can see from the commit status here, updating the dependencies _does_ mean having to address other code to accommodate for it. Updating `firebase` from v7...

Is this still happening? Maybe setting `entryPoint: "."` could help? Everything seems set up correctly from here though.

If you're stuck needing an older version of firebase-tools because of a node version, you can specify `firebaseToolsVersion` now. That should get you unstuck!

I think your question is better suited for the [Firebase Community](https://firebase.community), stack overflow, or the `firebase/firebase-tools` repo.

The version of firebase-tools can now be specified, if you need to stick on an older version.

That's a lot of info! Thanks for the logs. What's concerning to me is that the request to `https://accounts.google.com/o/oauth2/token` is simply failing to make the request - it's not returning...

This looks very reasonable. Would you mind catching it up with `main` and updating the branch? Thanks!

oh this nonsense. The tests that require secrets are going to fail because they won't work from a fork. I'll take care of that once you remove the tsconfig thing...