hyperfrontend.dev is built with Next.js, hosted on AWS.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries2 | ||
| 16.4.2 | 15 Nov 2026 | |
| – | 15 Nov 2026 | |
| Frontend Build Tools & CSS1 | ||
| – | 15 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks1 | ||
| CDN & Hosting2 | ||
| – | 15 Nov 2026 | |
| Accessibility1 | ||
| – | 15 Nov 2026 | |
| Donations & Fundraising1 | ||
| – | 15 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 15 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
What the homepage's first heading and body text render in, read from the browser's computed styles, and where the font files come from.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
smtp.google.comfortaleza.ns.porkbun.comcuritiba.ns.porkbun.commaceio.ns.porkbun.comsalvador.ns.porkbun.comgoogle-site-verification=qj6jM54USBecy7H3_LsbC6iCpQRQn7yAYSrqBVn8mzUsoloweave-verify=69ffdc72af04b24fbf4d30ea35c6b87egoogle-site-verification=n234MOqRWa89Wt9bEu99JJ311J12i7_tq85nlAab8DAUser-Agent: * Allow: / Sitemap: https://www.hyperfrontend.dev/sitemap.xml
# HyperFrontend > Compose your existing apps together securely, like Lego bricks. Every documentation page on this site has a Markdown counterpart at its own URL: append `.md` to the page route. The links below point straight at those files. ## Overview - [Architecture](https://www.hyperfrontend.dev/architecture.md): How the HyperFrontend libraries compose into one system. - [Acknowledgments](https://www.hyperfrontend.dev/docs/acknowledgments.md): The people and projects HyperFrontend is built on. - [@hyperfrontend/linter rule catalogue](https://www.hyperfrontend.dev/docs/libraries/linter/rules.md): Every rule @hyperfrontend/linter ships, with its options and examples. - [Manifesto](https://www.hyperfrontend.dev/docs/manifesto.md): Why HyperFrontend exists, where it is going, and what it will not build. - [Regarding AI](https://www.hyperfrontend.dev/docs/regarding-ai.md): HyperFrontend's position on AI-assisted development. ## Packages - [Builder](https://www.hyperfrontend.dev/docs/libraries/builder.md): Composable, vendor-neutral build toolkit for TypeScript libraries, JS bins, and Node SEA native binaries. - [Cryptography](https://www.hyperfrontend.dev/docs/libraries/cryptography.md): Production-grade cryptographic primitives with isomorphic APIs for browser and Node.js environments. - [Features](https://www.hyperfrontend.dev/docs/libraries/features.md): SDK, CLI, and dev server for building, embedding, and orchestrating hyperfrontend micro-frontend features. - [Linter](https://www.hyperfrontend.dev/docs/libraries/linter.md): A linter for TypeScript, JavaScript, JSX, JSON and Markdown with its own parsers and no external runtime packages. - [Logging](https://www.hyperfrontend.dev/docs/libraries/logging.md): Structured logging with configurable severity levels and error-resilient execution. - [Network Protocol](https://www.hyperfrontend.dev/docs/libraries/network-protocol.md): Production-grade network protocol for secure, real-time cross-window and cross-process communication with a session-keyed authenticated envelope, routing, and message queueing. - [Nexus](https://www.hyperfrontend.dev/docs/libraries/nexus.md): Secure cross-window communication library for micro-frontends with contract-validated messaging, origin-based security policies, and connection lifecycle management. - [Project Scope](https://www.hyperfrontend.dev/docs/libraries/project-scope.md): Comprehensive project analysis, technology stack detection, and transactional virtual file system for Node.js tooling. - [Questions](https://www.hyperfrontend.dev/docs/libraries/questions.md): Terminal prompting library with composable, functional API for text, select, confirm, and multiselect prompts - [State Machine](https://www.hyperfrontend.dev/docs/libraries/state-machine.md): Lightweight, functional state management library with Redux-inspired actions/reducers, async operation orchestration, and lifecycle-aware component abstractions for predictable application state. - [Testing](https://www.hyperfrontend.dev/docs/libraries/testing.md): A lightweight Jest-like testing library built on native Node capabilities. - [Data Utils](https://www.hyperfrontend.dev/docs/libraries/utils/data.md): Comprehensive data structure manipulation with circular reference handling and custom class support. - [Function Utils](https://www.hyperfrontend.dev/docs/libraries/utils/function.md): Higher-order function utilities for behavioral modification and composition. - [Immutable API Utils](https://www.hyperfrontend.dev/docs/libraries/utils/immutable-api.md): Decorators and utilities for creating immutable, tamper-proof object APIs with built-in prototype pollution defense. - [JSON Utils](https://www.hyperfrontend.dev/docs/libraries/utils/json.md): Zero-dependency JSON Schema Draft v4 validation and schema generation utilities. - [List Utils](https://www.hyperfrontend.dev/docs/libraries/utils/list.md): Purpose-built collection utilities for queue management, filtering, and iteration patterns. - [Random Generator Utils](https://www.hyperfrontend.dev/docs/libraries/utils/random-generator.md): Statistical random distributions and UUID generation for simulations, testing, and procedural content. - [String Utils](https://www.hyperfrontend.dev/docs/libraries/utils/string.md): Isomorphic string encoding utilities with unified APIs for browser and Node.js environments. - [Time Utils](https://www.hyperfrontend.dev/docs/libraries/utils/time.md): Functional time utilities for async operations, intervals, and time normalization. - [UI Utils](https://www.hyperfrontend.dev/docs/libraries/utils/ui.md): Modular DOM utilities for dynamic styling, gesture detection, element lifecycle, and color manipulation. - [Versioning](https://www.hyperfrontend.dev/docs/libraries/versioning.md): Versioning library with changelog parsing, conventional commits, and semver flow orchestration. - [Web Worker](https://www.hyperfrontend.dev/docs/libraries/web-worker.md): Web Worker utilities and abstractions. - [Workspace](https://www.hyperfrontend.dev/docs/libraries/workspace.md): Runs the tasks of a TypeScript monorepo and releases its packages from a graph of what reaches what. ## Architecture - [Builder architecture](https://www.hyperfrontend.dev/docs/libraries/builder/architecture.md): How @hyperfrontend/builder is put together, and why. - [Features architecture](https://www.hyperfrontend.dev/docs/libraries/features/architecture.md): How @hyperfrontend/features is put together, and why. - [Linter architecture](https://www.hyperfrontend.dev/docs/libraries/linter/architecture.md): How @hyperfrontend/linter is put together, and why. - [Network Protocol architecture](https://www.hyperfrontend.dev/docs/libraries/network-protocol/architecture.md): How @hyperfrontend/network-protocol is put together, and why. - [Nexus architecture](https://www.hyperfrontend.dev/docs/libraries/nexus/architecture.md): How @hyperfrontend/nexus is put together, and why. - [Project Scope architecture](https://www.hyperfrontend.dev/docs/libraries/project-scope/architecture.md): How @hyperfrontend/project-scope is put together, and why. - [State Machine architecture](https://www.hyperfrontend.dev/docs/libraries/state-machine/architecture.md): How @hyperfrontend/state-machine is put together, and why. - [Testing architecture](https://www.hyperfrontend.dev/docs/libraries/testing/architecture.md): How @hyperfrontend/testing is put together, and why. - [Versioning architecture](https://www.hyperfrontend.dev/docs/libraries/versioning/architecture.md): How @hyperfrontend/versioning is put together, and why. - [Workspace architecture](https://www.hyperfrontend.dev/docs/libraries/workspace/architecture.md): How @hyperfrontend/workspace is put together, and why. ## Guides and tutorials - [How to add your own executor and generator to a workspace](https://www.hyperfrontend.dev/docs/guides/add-your-own-executor-and-generator.md): A workspace needs checks and scaffolding particular to its own repository, and wants them run with the same command as the packaged targets rather than as loose scripts. - [How to base64 text that survives Unicode and URLs](https://www.hyperfrontend.dev/docs/guides/base64-for-unicode-and-urls.md): btoa either throws on emoji or quietly mangles accented text, and the base64 it does produce comes back percent-escaped when it travels in a query parameter. - [Build a setup wizard for your CLI](https://www.hyperfrontend.dev/docs/guides/build-a-setup-wizard-for-your-cli.md): My CLI takes its setup from a wall of flags nobody remembers, and every attempt at an interactive version turns into raw-mode handling, signal handlers, and a validation branch after every question. - [How to close a feature without losing unsaved work](https://www.hyperfrontend.dev/docs/guides/close-a-feature-without-losing-work.md): The host owns the frame and can tear it out whenever it likes, but only the embedded feature knows whether a draft, an armed timer, or an unsent edit is still inside, and removing an iframe fires nothing the feature can act on. - [How to compose independently shipped features on one page](https://www.hyperfrontend.dev/docs/guides/compose-independent-features.md): I need several independently built, independently deployed apps working together on one page, coordinating with each other, without merging codebases and without one failure taking down the rest. - [How to detect and handle an unresponsive feature](https://www.hyperfrontend.dev/docs/guides/detect-unresponsive-feature.md): An embedded feature can hang, crash, or lose its tab throttling fight; I need the host to notice within seconds, tell the user honestly, and recover when it returns. - [How to embed a feature someone else shipped](https://www.hyperfrontend.dev/docs/guides/embed-a-shipped-feature.md): Another team shipped their app as a feature package; I need it running inside my page, alive and observable, without learning their stack. - [How to encrypt and decrypt a string with a password](https://www.hyperfrontend.dev/docs/guides/encrypt-a-string-with-a-password.md): I need to store an API key, a token, or a note encrypted under a password, and I do not want to hand-roll key derivation, salts, and initialisation vectors around the Web Crypto API. - [How to fingerprint content with a hash](https://www.hyperfrontend.dev/docs/guides/fingerprint-content-with-a-hash.md): I need a stable id for a piece of content so I can skip work I already did or ask the other side whether it already has this exact thing, and the browser and the server keep computing that id two different ways. - [How to make your first cross-window connection](https://www.hyperfrontend.dev/docs/guides/first-cross-window-connection.md): I have a page and an iframe that need to talk to each other, and raw postMessage keeps turning into stringly-typed guesswork that breaks in production. - [How to fix "Converting circular structure to JSON"](https://www.hyperfrontend.dev/docs/guides/fix-converting-circular-structure-to-json.md): JSON.stringify throws on an object graph with back references, the engine names only one of them, and every edge I remove reveals another. - [How to generate values that look natural instead of random](https://www.hyperfrontend.dev/docs/guides/generate-values-that-look-natural.md): Everything I generate with Math.random comes out looking mechanical: sizes are spread evenly instead of clustering around a typical one, jitter is as likely to be huge as tiny, and spawned things arrive on a metronome no crowd ever moves to. - [How to harden your code against prototype pollution](https://www.hyperfrontend.dev/docs/guides/harden-code-against-prototype-pollution.md): Anything else running on the page can add to Object.prototype or reassign a built-in like Array.isArray, and my authorisation checks, serialisers, and dispatch tables inherit the lie without an error anywhere. - [Build a CLI with a --verbose mode](https://www.hyperfrontend.dev/docs/guides/instrument-a-cli-with-logging.md): My command line tool is either silent or drowning in console.log, the diagnostics land on stdout where they break every pipe, and when a run fails I cannot tell which stage went wrong or how long it took. - [How to lint a project with @hyperfrontend/linter](https://www.hyperfrontend.dev/docs/guides/lint-a-project-with-hyperfrontend-linter.md): A project needs its code checked and fixed against agreed rules, without bringing a parser, plugins and their dependency trees into every install. - [How to make a service safe to use before it is ready](https://www.hyperfrontend.dev/docs/guides/make-a-service-safe-to-use-before-it-is-ready.md): A shared service with async setup only ever serves one of its two callers: whoever subscribed early waits for a signal, and whoever subscribed late missed the signal that already fired, so I end up guarding every call site with an isReady check that can go stale between the check and the subscribe. - [How to migrate a Jest suite to Node's test runner](https://www.hyperfrontend.dev/docs/guides/migrate-from-jest-to-node-test.md): Jest pulls a framework, a transformer and a reporter stack into a project whose runtime already ships a test runner, but rewriting thousands of Jest-style tests into node:test calls is not an option. - [How to migrate from v1 and v2 to v3 and v4](https://www.hyperfrontend.dev/docs/guides/migrate-from-v1-and-v2-to-v3-and-v4.md): My host and feature pin protocol v1 or v2, and the current releases only build and negotiate v3 and v4. I need to move both sides without losing the mode I had, and know what the app will observe once the channel is keyed per session. - [How to pause and resume a countdown](https://www.hyperfrontend.dev/docs/guides/pause-and-resume-a-countdown.md): My idle timeout has to stop while a dialog is open and continue from where it stopped, and every version I write with setTimeout drifts or restarts by accident. - [Publish a TypeScript library to npm](https://www.hyperfrontend.dev/docs/guides/publish-a-typescript-library-to-npm.md): Shipping a TypeScript library means an exports map, ESM and CJS builds, and a declaration pass that all have to agree, and every one of them is hand-maintained until it silently stops matching what was emitted. - [How to publish release notes from your CHANGELOG.md](https://www.hyperfrontend.dev/docs/guides/publish-release-notes-from-your-changelog.md): My release job has a version and a CHANGELOG.md, and every attempt to get one from the other is a regex over markdown headings that breaks the first time an entry carries a compare link, a scope, or a breaking marker. - [How to read another tool's config file](https://www.hyperfrontend.dev/docs/guides/read-another-tools-config-file.md): My tool needs to read a project's tsconfig, bundler, or environment configuration, and every attempt turns into a list of seven candidate filenames per tool plus a JSON.parse that throws on the comments TypeScript allows. - [How to release libraries from their commits](https://www.hyperfrontend.dev/docs/guides/release-libraries-from-their-commits.md): Versions and changelogs written by hand drift from what the commits changed, and nothing stops a push whose versions are wrong. - [How to replace commitizen and commitlint with one package](https://www.hyperfrontend.dev/docs/guides/replace-commitizen-and-commitlint.md): Guided commit authoring and commit-message linting take four packages and two config files that have to be kept agreeing with each other, and the prompt still offers types the linter rejects. - [How to replace ESLint with @hyperfrontend/linter](https://www.hyperfrontend.dev/docs/guides/replace-eslint-with-hyperfrontend-linter.md): ESLint, its parser and its plugins put dozens of packages into every install of a project whose checks fit a smaller set of rules, and removing them must not quietly drop a check the project depends on. - [How to run async jobs one at a time, in order](https://www.hyperfrontend.dev/docs/guides/run-async-jobs-one-at-a-time.md): My writes need to happen one at a time and in order, and the array-plus-busy-flag queue I wrote breaks the moment a second caller starts it, a rejected job leaves the flag stuck, or a retry queues the same work twice. - [How to configure and run TypeScript tests on Node's test runner](https://www.hyperfrontend.dev/docs/guides/run-typescript-tests-on-node-test.md): node:test runs TypeScript files through type stripping, but it resolves no extensionless imports or path aliases, has no environment concept for a DOM, and lets a file nobody tested through a full-coverage gate. - [Set up a monorepo and test only what changed](https://www.hyperfrontend.dev/docs/guides/set-up-a-monorepo-and-test-only-what-changed.md): A repository of several TypeScript libraries runs every test on every change, because nothing knows which libraries a change actually reaches. - [How to style a widget you inject into someone else's page](https://www.hyperfrontend.dev/docs/guides/style-a-widget-you-inject-into-someone-elses-page.md): My widget ships as one script into markup I do not own, and the style tag it injects has no owner: mounting twice leaves two copies, and unmounting leaves the rules behind. - [How to test a package the way a consumer installs it](https://www.hyperfrontend.dev/docs/guides/test-a-package-the-way-a-consumer-installs-it.md): My library passes every test in the workspace, where path aliases, loader hooks and a hoisted node_modules resolve whatever the source asks for, and then a consumer runs npm install and the published entry fails to load or throws on the first call. - [How to test interactive prompts without a terminal](https://www.hyperfrontend.dev/docs/guides/test-interactive-prompts-without-a-terminal.md): My CLI's prompts are the only part of it with no tests, because a test runner has no TTY to give them and driving raw keystrokes from a spawned process is more machinery than the code being tested. - [How to track an async task without loading flags](https://www.hyperfrontend.dev/docs/guides/track-an-async-task-without-loading-flags.md): isLoading and error cannot tell a background refresh from a first load or a retry from a fresh failure, so my spinner hides rows I already had and my error banner vanishes the moment someone clicks retry. - [Troubleshooting a secured channel](https://www.hyperfrontend.dev/docs/guides/troubleshoot-a-secured-channel.md): A channel that pins a security envelope is not behaving as I expect: messages go missing, a handshake is refused, the session closes on its own, a call throws about the shared key, or an error carries a code I do not recognise. - [How to validate a config file at startup](https://www.hyperfrontend.dev/docs/guides/validate-a-config-file-at-startup.md): A wrong value in a config file does not fail where it is written, it fails hours later somewhere unrelated, and fixing one mistake only reveals the next one. - [How to write and test a custom lint rule](https://www.hyperfrontend.dev/docs/guides/write-and-test-a-custom-lint-rule.md): A team needs a check the packaged lint rules do not make, with a fix where one is safe, and needs it to keep behaving as intended as the code around it changes. - [How to write focused tests with mocks, fake timers and module replacements](https://www.hyperfrontend.dev/docs/guides/write-focused-tests-with-mocks-and-fake-timers.md): My tests pass, but when one fails I cannot tell what broke: each test checks several things, timers are awaited for real, and the module a function depends on cannot be replaced without restructuring the code. ## Articles - [Complete Architectural Sovereignty](https://www.hyperfrontend.dev/articles/complete-architectural-sovereignty.md): An argument for owning more of your software, knowing when not to, and reconsidering some of the assumptions we've inherited from modern dependency culture. - [Hyperfrontend: The Long Way Around](https://www.hyperfrontend.dev/articles/hyperfrontend-the-long-way-around.md): The code is nine months old. The ideas behind it took ten years, and every package exists because something else needed it first. - [HyperFrontend vs. Module Federation: Two Very Different Answers to the Same Microfrontend Problem](https://www.hyperfrontend.dev/articles/hyperfrontend-vs-module-federation.md): Both let teams ship independently and compose at runtime. The resemblance mostly ends there. - [I Replaced ESLint. The First Attempt Worked. I Threw It Away.](https://www.hyperfrontend.dev/articles/i-replaced-eslint-the-first-attempt-worked-i-threw-it-away.md): Removing dependencies was easy compared with deciding how much of their code I actually wanted to own. - [I Replaced Jest With 1,200 Lines of Code. I'd Do It Again.](https://www.hyperfrontend.dev/articles/i-replaced-jest-with-1200-lines-of-code.md): Moving 11,900 tests from Jest onto node:test removed 457 packages from the lockfile, found product bugs the old runner had hidden, and c
| – |
| 15 Nov 2026 |
| – |
| 15 Nov 2026 |