next.js
51defb24 - provide the PORT env var based on server port, update turbopack (#48347)

Commit
2 years ago
provide the PORT env var based on server port, update turbopack (#48347) ### What? gives user code access to `process.env.PORT` as current server port avoid injecting env vars into code on server ### Why? it might need construct an addr to fetch from api routes fixes WEB-868 ### Turbopack changes * https://github.com/vercel/turbo/pull/4565 <!-- Tobias Koppers - Bind to IPv6 and IPv4 --> * https://github.com/vercel/turbo/pull/4570 <!-- Tobias Koppers - review follow ups --> * https://github.com/vercel/turbo/pull/4585 <!-- Tobias Koppers - fixup bind v6 PR: add missing listen call --> * ~https://github.com/vercel/turbo/pull/4546~ <!-- Alex Kirszenberg - Chunking Context Refactor pt. 3: Address PR comments from pt. 2 --> * https://github.com/vercel/turbo/pull/4580 <!-- Tobias Koppers - remove circular dependency --> * https://github.com/vercel/turbo/pull/4582 <!-- Tobias Koppers - ignore internal and server-relative url() in CSS --> * https://github.com/vercel/turbo/pull/4579 <!-- Tobias Koppers - make node bootstrap asset lazy --> * https://github.com/vercel/turbo/pull/4581 <!-- Tobias Koppers - allow to create stress test for client components --> * https://github.com/vercel/turbo/pull/4584 <!-- Tobias Koppers - improve node.js receive timeout --> * https://github.com/vercel/turbo/pull/4583 <!-- Tobias Koppers - remove panic since this might happen due to eventual consistency --> fixes WEB-871
Author
Parents
Loading