Fastify update - #79
Merged
Merged
Conversation
…nav, htmx boost, readme updates, license change
…nd to watch concurrently
…loading current URL Immediate reload on 'controlling' caused a black screen on long-lived htmx-boosted pages. The new SW takes control mid-session before it can serve in-flight requests, resulting in a blank response. Instead, set a flag when the SW update takes control and defer the transition to the user's next boosted htmx GET navigation. The htmx XHR is cancelled via event.preventDefault() and replaced with a full page navigation to the intended destination. Checks for boosted=true to avoid intercepting partial hx-get requests (polls, lazy loads, filters) which would otherwise navigate the full page to a fragment URL.
…s sdk v3 with aws-sdk/lib-storage upload class for handling chunked streaming uploads
* autocannon load testing * tsconfig exclude scripts folder * path fixes
* fastify first cut * delete pwa.spec * commonjs module resolution for fastify res.view method declaration, to align closer with official docs * fix pipeline, update documentation * rolled back wildcard pattern change * Added back documentation comments in main.ts * fixed auth redirects by manually setting value to 302 * formatting * req.hostname -> back to req.host * refactor: replace view-context interceptor with fastify reply.locals preHandler hook Replace the NestJS ViewContextInterceptor with a Fastify preHandler hook that populates reply.locals, matching the Express res.locals pattern. This provides uniform request-scoped context to all views (@Render and reply.view alike) without controller-level boilerplate. - Add preHandler hook in main.ts to build context once per request - Delete ViewContextInterceptor and remove APP_INTERCEPTOR registration - Update manual reply.view() calls in AuthController to spread reply.locals - Remove ViewContextService dependency from AuthController - Update ErrorViewFilter to read reply.locals directly with fallback - Fix req.hostname -> req.host for correct port-inclusive URLs * commenting express like res.locals equivalent for fastify * envs and loopback trusting * drain streams before mimetype error * normalized baseUrl variable in locals viewcontext * pinned playwrite action node version and gitignore autocannon results
- added node_modules/sortablejs to static assets
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
1 participant
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.
This Fastify migration has yielded nearly a 2x throughput increase and almost halfed the latency.
Before
After