Closed simondotm closed 7 months ago
I dug a little bit deeper and found that around the time that you started seeing this behavior (end of may), the https://github.com/GoogleCloudPlatform/buildpacks/issues/193#issuecomment-1570604865. They state that you would need to have the @google-cloud/functions-framework dependency installed, like the error gives.
A comment from an issue in firebase tools. Seems like pnpm
is supported, but that dependency needs to be added.
We'll likely need to add this to the plugin initialiser then.
Originally posted by @Lowell20 in https://github.com/simondotm/nx-firebase/issues/193#issuecomment-2018869760
I'm quite interested in
pnpm
compatibility, and I'm currently trying to migrate this plugin to it at the moment, mainly for speed reasons with CI & e2e/compatibility testing.In terms of pnpm support for firebase functions in Nx workspaces that use pnpm, I think it should just work.
As far as I can tell, as long as Nx knows the workspace package manager is
pnpm
it will generate a pruned `pnpm-lock.yaml' for firebase functions built with esbuild (from Nx 16.8.1+ anyway).If the workspace package manager is npm, it will generate a pruned
package-lock.json
instead.I've yet to try deploying a function with
pnpm-lock.yarn
, so would be interested to know if anyone in the community has got this working.