ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Determine whether k6 should extend its HTTP module with built‑in token refresh logic to automatically handle expired bearer tokens or API keys during a load test. Constraints The current core runtime leaves authentication entirely to the test script; adding automatic refresh would introduce runtime dependencies, version‑sensitive behavior, and potential
Runtime Request Handling Bun provides a native implementation of the Web Standard Fetch API alongside a compatibility layer for the Node.js http and https modules. While these coexist to support legacy migration, they utilize different underlying mechanisms for request execution and header management. Specification Consistency When migrating from Node.js-sty
The transition from k6 v0.47 to v0.50 introduced significant shifts in how the HTTP module handles implicit behaviors. Specifically, changes to default timeouts, redirect handling, and connection reuse logic create a compatibility boundary for scripts that relied on previous version-level defaults. When upgrading without explicitly defining these options in
bun
k6