You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recommend using a Procfile because it takes npm or yarn out of the path.
This makes me think that maybe, it should be somehow possible to alter default /bin/bash -c yarn functions-framework command into something more yarn pnp friendly, possibly by providing some form of custom procfile in the code deployed?
Alternatively - maybe there is some other issue in zero install mode? we do have workspace-tools plugin installed, and verified that yarn workspaces focus --all --production gets called during cloud function build process.
The text was updated successfully, but these errors were encountered:
We experience about 2x memory usage when using cloud function in yarn 2 plug and play, zero install mode.
node -r ./.pnp.cjs ...
without calling yarn directly should help mitigate this problem.This makes me think that maybe, it should be somehow possible to alter default
/bin/bash -c yarn functions-framework
command into something more yarn pnp friendly, possibly by providing some form of custom procfile in the code deployed?Alternatively - maybe there is some other issue in zero install mode? we do have workspace-tools plugin installed, and verified that
yarn workspaces focus --all --production
gets called during cloud function build process.The text was updated successfully, but these errors were encountered: