Daniel Lee

Thanks for reporting the issue @shalbert94 and @jankalthoefer. A workaround would be to wrap the error stack inside a simple object: ```js const functions = require('firebase-functions'); try { throw new...

@shalbert94 Thanks for making the suggestions. I think that makes for a good FR. I don't think we can prioritize the work ATM, but feel free to check in with...

Hi @SrBrahma. I'm not sure what is being asked here - can you clarify for us? For wrapped functions allows you to pass arbitrary javascript object under the `auth` property....

Based on the error message received, it looks like the version of `node` binary that is used as part of `firebase deploy` isn't using version of `node` that understands optional...

@alexleonov-tactiq Thanks for the clue and additional prompts folks. I'll see if I can reproduce the issue today.

@ts95 Sorry for the troubles. I think we need to improve on emitting better debug logs that helps with debugging the underlying issue. I remember helping another customer with an...

@GarrickBrown Do you mind sharing your setup with us? (Are you using pnpm or other monorepo tooling by any chance?) In this particular issue, version of the firebase-functions package is...

Hey @0xjei - thanks for reporting and apologies for the issue you are seeing. I tried giving 16GiB function a spin and it gave my setup no problem: ``` exports.sixteen...

@0xjei Yes it should be working in both cases. Thank you for your detailed feedback - I'll go back and see what I can uncover.

I played around with several settings, and at least locally on my machine: ``` import { onCall } from "firebase-functions/v2/https"; export const shake = onCall({ memory: "16GiB"}, () => "hello");...