Merged
Conversation
|
@nafiuishaaq Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added a middleware benchmark harness in the middleware workspace with one benchmark file per exported middleware, automated coverage verification against src/index.ts, and a report writer for PERFORMANCE.md. The main pieces are run-all.cjs, benchmark-runner.cjs, and verify-coverage.cjs. I also added benchmark definitions for jwt-auth.middleware.benchmark.cjs, timeout.middleware.benchmark.cjs, and circuit-breaker.middleware.benchmark.cjs, plus package scripts in package.json.
I was able to verify export coverage with node benchmarks/middleware/verify-coverage.cjs, and it confirms every currently exported middleware has a matching benchmark file. I was not able to generate real latency numbers or fill the markdown table with measured p99 deltas because this workspace still lacks installed runtime/build dependencies, and the install request was not approved. Because of that, PERFORMANCE.md is committed with the correct table structure and pending rows rather than fabricated results.
Closes #350