Mael
Mael
I confirm I still have the issue with the latest packages, here are the packages I'm importing: ``` "dependencies": { "@eslint/eslintrc": "3.1.0", "@eslint/js": "9.5.0", "@google-cloud/firestore": "7.9.0", "@google-cloud/functions-framework": "3.4.1", "@gouach/backend-utils": "workspace:*",...
And here's the output of `cat pnpm-lock.yaml|grep google | pbcopy` ``` '@google-cloud/error-reporting': google-auth-library: google-spreadsheet: version: 4.1.2([email protected]([email protected])) googleapis: '@google-cloud/firestore': '@google-cloud/functions-framework': '@google-cloud/logging': eslint-config-google: '@google-cloud/firestore': eslint-config-google: '@google-cloud/[email protected]': '@google-cloud/[email protected]': '@google-cloud/[email protected]': '@google-cloud/[email protected]': '@google-cloud/[email protected]': '@google-cloud/[email protected]': '@google-cloud/[email protected]':...
I guess I'm running just off-the-shelf cloud functions, they are defined liked this: ``` export const desiredStateUpdateTrigger = onDocumentUpdated( { document: `${dbCollectionNames.batteryBMS}/{id}`, vpcConnector: isProduction ? "api-pingo-connector" : undefined, vpcConnectorEgressSettings: isProduction...
I don't think it's linked to any particular data, because this happens in ANY of my "onDocumentUpdated" methods, which have very different data and schemas I think the protobuf encoding/decoding...
This is my tsconfig in case ``` { "compilerOptions": { "target": "ESNext", "module": "ESNext", "moduleResolution": "Bundler", "composite": true, "noImplicitReturns": true, "noUnusedLocals": true, "allowJs": true, "strict": true, "skipLibCheck": true, "types": ["node"],...
and I'm using the "isolate" package to move local monorepo pnpm dependencies in the local "cloud functions" dir when deploying on Firebase (otherwise it doesn't find local dependencies) https://www.npmjs.com/package/isolate-package Here's...
(also I don't know why this error doesn't seem to trigger an "error report email" from GCloud which I normally have when my cloud function fail)
@exaby73 so I investigated some more, and it doesn't seem to be an import version of a lib or whatever, but rather the import order. My functions is an index.ts...
absolutely no idea why - the "someFileWhichCausedIssues" was located because if I removed it from the imports originally, the other cloud functions would start working, but if I put it...
could it be related to what I'm seeing at https://github.com/drizzle-team/drizzle-orm/issues/4361