Skip to content

Add Nifra framework benchmarks - #848

Closed
TechDev009 wants to merge 2 commits into
e18e:mainfrom
TechDev009:codex/add-nifra-benchmarks
Closed

TechDev009 wants to merge 2 commits into
e18e:mainfrom
TechDev009:codex/add-nifra-benchmarks

Conversation

@TechDev009

@TechDev009 TechDev009 commented Nov 13, 2026 •

Copy link
Copy Markdown

Summary

Add Nifra starter and runtime fixtures, registry/configuration, benchmark runners, docs, and logo.

The production path now stays on Nifra's fast implementation:

Nifra starter/app
    -> Bun-native Nifra build with the Node target
    -> .nifra-node
    -> @nifrajs/node direct app lane (app.resolveNode)
    -> direct Web app.fetch only for in-process SSR throughput

Evidence

  • Before: Nifra had no starter, runtime app, registry entry, or benchmark runner.
    After: Nifra is wired into install/build/dev/browser/SSR/SSR-load/router-link measurements with exact 5.13.0 pins.
  • Before: the runtime wrapped a generated Vercel fetch function as { fetch }, hiding the Node-direct lane.
    After: the runtime serves the built app object directly, and the in-process handler imports that same native build.
  • Before: docs had no Nifra page or methodology entry.
    After: /framework/nifra/, logo, methodology, and README data links are included.

Verified locally:

  • pnpm run type-check and pnpm run build in packages/starter-nifra and packages/app-nifra
  • nifra check --json in both packages
  • direct app.resolveNode and HTTP/static-asset smoke checks
  • one direct Nifra SSR throughput run
  • pnpm --config.engine-strict=false --filter @framework-performance/stats-generator lint
  • pnpm --config.engine-strict=false --filter @framework-performance/stats-generator test (83 passing)
  • pnpm --config.engine-strict=false --filter @framework-performance/docs build
  • Browser Lighthouse runs were not executed locally because Chrome is not installed; CI is expected to run them.

Merge Danger

Door: two-way
Blast Radius: benchmark-only

@AlexanderKaran

Copy link
Copy Markdown
Collaborator

Hi @TechDev009

Thank you for the PR. We actually have a process for adding new benchmarks: https://github.com/e18e/framework-performance/blob/main/CONTRIBUTING.md#adding-a-new-framework

Please give it a read and follow the steps. Will close this PR for now.

@TechDev009

Copy link
Copy Markdown
Author

@AlexanderKaran ok let do that

This was referenced Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants