Developing, testing, and defining the runtime Web APIs for Edge infrastructure.
by vercelTypeScript
Last 12 weeks · 0 commits
3 of 6 standards met
Bug Report Package: Version observed: Current behavior When converting a Node.js into a Fetch , the function only reads . In HTTP/2 connections, the request authority is often provided via the pseudo-header instead, leaving the header unset. As a result, the adapter falls back to the , causing to point to the wrong host even when the client provided the correct authority. Expected behavior/code should reflect the client's authority (e.g., ) when the pseudo-header is present in the request headers. Possible solution** Update to check for the header if is missing, and improve protocol inference to better handle TLS on non-standard ports.
Summary parse the first name/value pair without routing it through the request-cookie parser decode response cookie values exactly once, falling back to the raw value for malformed percent escapes add regressions for , bare , valueless pairs, and values containing This fixes the cookie parsing failure reported from Next.js middleware/runtime usage in vercel/next.js#70523. Tests
Bug Report Current behavior Within the edge runtime calling ( is equivalent, see additional context) returns an anonymous function . You can reproduce this behavior here: Returns: Expected behavior/code In both browser and node runtimes, using returns . I have a feeling like it should work in a edge runtime as well 🤔 Possible solution I nailed it down to this proxy and similarly for however, I couldn't figure out a solution for it 😞 Additional context/screenshots For background context, I found this using the lib, which was using 's function, specifically this line: https://github.com/lodash/lodash/blob/4.17.15/lodash.js#L12046 (directly ). I've been debating whether that is unreliable to use on lodash's library or something broken by the runtime. I have a feeling like this is something the runtime should fix since it works as expected on /browser runtimes but let me know otherwise.
Repository: vercel/edge-runtime. Description: Developing, testing, and defining the runtime Web APIs for Edge infrastructure. Stars: 912, Forks: 91. Primary language: TypeScript. Languages: TypeScript (87.9%), JavaScript (12.1%). License: MIT. Homepage: https://edge-runtime.vercel.app Latest release: edge-runtime@4.0.1 (1y ago). Open PRs: 25, open issues: 28. Last activity: 3mo ago. Community health: 62%. Top contributors: dependabot[bot], Kikobeats, github-actions[bot], Schniz, balazsorban44, javivelasco, feugy, leerob, nkzawa, smaeda-ks and others.