Matthew Robertson

The workaround here is to drop a file named `project.toml` into the root of your project with the following content: ``` [[build.env]] name = "GOOGLE_NODE_RUN_SCRIPTS" value = "" ``` Explanation:...

I don't think we need to wait for `google-24` to make this change. All other runtimes default to the latest available version and parse framework configs / env vars for...

Sounds like the orginal issue reported here was resolved by https://github.com/GoogleCloudPlatform/buildpacks/pull/219

@xSAVIKx is right, we do fetch the code differently on GAE and GCF. On GAE we use a custom build step that runs [the gcs-fetcher](https://github.com/GoogleCloudPlatform/cloud-builders/tree/master/gcs-fetcher). I guess we would need...

According to [the npm docs](https://docs.npmjs.com/cli/v8/commands/npm-prune), it seems we are doing the right thing: > If the --production flag is specified or the NODE_ENV environment variable is set to production, this...

I just tested and the debugging works fine as documented. Perhaps there was an issue with your `npm install`?

We have a guide in docs that described how to use ESM: https://github.com/GoogleCloudPlatform/functions-framework-nodejs/blob/main/docs/esm.md I don't think we want to pull this into the main README as we want to keep...

overall this LGTM. Please remove the --signature-type flag and we can merge.

Thank you for the detailed bug report @Standaa . I took a quick look into our [Procfile processing code](https://source.corp.google.com/piper///depot/google3/third_party/gcp_buildpacks/cmd/config/entrypoint/main.go;l=111?q=%20addProcfileProcesses), and it looks like we require a `web` entry because we...

The issue of not having a way to directly access node content did cross my mind, but I think you can take this from context in the templating. For example...