rsnext/packages
AdamKatzDev 9dbd8d7741
feat(standalone): allow configuring KEEP_ALIVE_TIMEOUT via env var (#46052)
Resolves #39689, partially resolves #28642 (see notes below)
Inspired by #44627

In #28642 it was also asked to expose `server.headersTimeout`, but it is
probably not needed for most use cases and not implemented even in `next
start`. It was needed to change this option before
https://github.com/nodejs/node/issues/27363.
There also exists a rare bug that is described here
https://github.com/nodejs/node/pull/32329#issuecomment-614119125. To fix
this exposing `server.headersTimeout` might be required both in
`server.js` and in `next start`.

Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-03-17 11:22:43 -07:00
..
create-next-app v13.2.5-canary.7 2023-03-17 13:31:21 +01:00
eslint-config-next v13.2.5-canary.7 2023-03-17 13:31:21 +01:00
eslint-plugin-next v13.2.5-canary.7 2023-03-17 13:31:21 +01:00
font v13.2.5-canary.7 2023-03-17 13:31:21 +01:00
next feat(standalone): allow configuring KEEP_ALIVE_TIMEOUT via env var (#46052) 2023-03-17 11:22:43 -07:00
next-bundle-analyzer v13.2.5-canary.7 2023-03-17 13:31:21 +01:00
next-codemod v13.2.5-canary.7 2023-03-17 13:31:21 +01:00
next-env v13.2.5-canary.7 2023-03-17 13:31:21 +01:00
next-mdx v13.2.5-canary.7 2023-03-17 13:31:21 +01:00
next-plugin-storybook v13.2.5-canary.7 2023-03-17 13:31:21 +01:00
next-polyfill-module v13.2.5-canary.7 2023-03-17 13:31:21 +01:00
next-polyfill-nomodule v13.2.5-canary.7 2023-03-17 13:31:21 +01:00
next-swc v13.2.5-canary.7 2023-03-17 13:31:21 +01:00
react-dev-overlay v13.2.5-canary.7 2023-03-17 13:31:21 +01:00
react-refresh-utils v13.2.5-canary.7 2023-03-17 13:31:21 +01:00