-
Notifications
You must be signed in to change notification settings - Fork 2k
feat: add ultimate express #9390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
NateBrady23
merged 15 commits into
TechEmpower:master
from
Pho3niX90:feature/add_uexpress
Dec 13, 2024
Merged
Changes from 1 commit
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
98c2a34
feat: add ultimate express
Pho3niX90 11e2bd7
feat: add ultimate express
Pho3niX90 d468cd8
refactor(express): simplify response handling by removing writeRespon…
Pho3niX90 16db140
fix: unique display names
Pho3niX90 96bba27
fix: names
Pho3niX90 b1ea37d
fix: add db/query/update/fortune urls
Pho3niX90 d45b608
fix: missing orm value
Pho3niX90 543092f
fixes
Pho3niX90 3017dc6
fixes
Pho3niX90 c752e2a
fixes
dimdenGD c89ade1
full refactor
dimdenGD fcdf324
fix etag and disable x-powered-by
dimdenGD 4fcc1db
generate json dynamically
dimdenGD b9b29fa
fix space
dimdenGD 8f5b177
use fjs
dimdenGD File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fast-json-steingify is faster than slow-json-stringify with "unsafe" string type https://www.npmjs.com/package/fast-json-stringify
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't find a benchmark for that
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have made it here https://stackblitz.com/edit/stackblitz-starters-rlrggo
for small json
JSON.stringifyis faster,slow-json-stringifyis always slow. Side note "fast-json-stringify: unfafe" is raw fast-json-stringify with no special chars support on string (\n,\r,\t,",\),Hello, World!no need escape.Use
JSON.stringify, this libraries (fast-json-stringifyandslow-json-stringify) works better on complex/huge jsonslow-json-stringify last update is 4 years ago (maybe is abbandoned)
fast-json-stringify is active and mantained fy Fastify team
The better option is send as raw/stringified string
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You must serialize JSON in the request as per test rules. Your benchmark has a bug and doesnt serialize object properly, I fixed and tested it and it seems that fast-json-stringify is still fastest, so I switched it over.