Matthew Robertson

confirmed on Chrome and Chrome Canary on OSX

@dimmetrius this is a [long standing issue with NPM](https://github.com/npm/npm/issues/4603). By default the nodejs buildpacks will run your app by calling `npm run start`. Unfortunately this causes `npm` to swallow SIGTERM....

@steren I agree on 2. I have re-opened the issue. On 1, I don't think we can change the default behaviour as `npm start` has a bunch of side effects...

We release updates to the base images very frequently. Could you please share the details of which CVEs you are finding in the images and how you are scanning? AR...

I agree we need better documentation on how to rebase to update the base image layers. We should also provide docs on how to remove unnecessary packages from the base...

Thanks for reporting this @steverandy. Could you tell me more about how you were building the app when the when the dev dependencies were not pruned? Were you deploying to...

sounds like this if fixed

+1 If you have a multipage application you need the `force` to persist across page loads. I might take a whirl at adding this.

I think we shouldn't be passing around value constructs at runtime in order to influence the TS type checker. The TS type system only exists at compile time. Passing around...

I updated the docs. You should configure the `main` field to point to your compiled source code.