A new JavaScript framework is generated every time you load the page. All are equally real. All are equally unnecessary.
We started building this after realising that existing framework generators were great — for the use cases their authors had when they built them. But the JavaScript ecosystem has changed.
We didn't set out to build a framework generator. We set out to build a small satirical tool. One weekend later, here is the framework generator.
The core API surface is intentionally small. Everything else is just composition. If you've read the source, you've read the generator.
In our benchmarks, this generator is 40% faster than React. Benchmark methodology available here. (under review)
Each page load produces a complete, production-ready JavaScript framework:
| Feature | How |
|---|---|
| Framework name | 26 prefixes × 16 middles × 7 suffixes. Every combination sounds real because all real framework names are the same 50 words rearranged |
| Tagline | Template substitution with adjectives like "ergonomic", "resumable", "isomorphic" — the full LinkedIn bingo card |
| Version | v0.x.y-beta.z. v1.0 is planned. Timeline TBD. |
| Benchmarks | Always beats React by 18–42%. Measured on a warm M2 under optimal conditions. Your production numbers may vary. By a lot. |
| Manifesto | 5 paragraphs. All 5 are accurate for every JavaScript framework ever created. |
| Discord stats | 30–55% of members are the author on alternate accounts. This is industry standard. |
| "Used by" logos | "Acme Corp", "Probably A Startup", "Undisclosed Client". Verification not available at this time. Or any time. |
| Migration guide | 47 pages. Steps 1–3 involve unlearning React. |
| Layer | Choice | Notes |
|---|---|---|
| HTML | Yes | — |
| CSS | Yes | — |
| JavaScript | Yes | — |
| Framework | None | Considered ironic |
| Build tool | None | — |
| npm packages | 0 | We are very proud of this |
| Bundle size | 1 .html file |
Lighthouse: flawless |
| Weekly downloads | Procedurally generated | 87–97% are transitive deps |
# Clone
git clone https://github.com/portelldx/js-framework-generator
# Install dependencies
# (there are none)
# (this took 0ms)
# (we'd like to acknowledge this achievement)
# Run
open index.htmlYour new framework is ready. It is already faster than React. The docs are 3 pages.
// Click "Generate Another Framework"
// Or reload the page
// Each reload produces a different framework
// All are production-ready
// None have been used in production
// This is not a coincidence- Procedural framework name generation
- Benchmarks where the new framework always wins
- Manifesto (all 5 paragraphs accurate for all frameworks)
- Fake Discord member counts
- "Trusted by" logos (unverifiable)
- Migration guide (47 pages, unwritten)
- v1.0 (planned, timeline not planned)
- Actual documentation (see above)
- Make benchmarks slightly less obviously fake (won't fix)
- Understand why this feels exactly like real framework marketing (investigating)
Is any of this a real framework? Every framework generated by this tool is as real as any framework released in the last 3 years.
Why does the new framework always beat React in benchmarks? Because all new frameworks beat React in the benchmarks they design for themselves. We are simply more honest about the process.
Can I use a generated framework in production? The framework is generated. The hubris required to deploy it is entirely your own.
I refreshed and got a different framework. Which one should I use? Yes.
Will there be a v1.0? v1.0 is planned. The timeline is not. We're building in the open. Stars appreciated.
Is this making fun of the JavaScript ecosystem? We prefer "affectionate documentation."
Also zero dependencies. Also built in a weekend. Also asking uncomfortable questions about your choices:
Vibe Check → Find out which developer archetype you are. Results are ruthlessly accurate.
Zero npm dependencies · All data is fake · All descriptions are real · A new JS framework born every 72 hours, whether we need one or not