FlexDoc
Try ExpressGitHub ↗
FlexDoc releases

Release notes.

Latest JavaScript product release: FlexDoc 3.5.0. Spring / Java 0.11.0. ASP.NET Core 0.8.0. Package versions are independent across ecosystems.

What's new All versions
Latest releaseSeptember 22, 2026

FlexDoc 3.5.0

FlexDoc 3.5 names an undocumented runtime route, fails the default check, shows the contract gap beside the registration, and opens that route in the API Client.

Release notes Renderer .tar.gz Docs for 3.5
Install FlexDoc 3.5.0
What's new

Changes by release

There were no standalone JavaScript packages for 2.4 through 2.7. Their changes are included here so the history stays complete; the Versions section lists only builds that were actually published.

FlexDoc 3.5
Released as 3.5.0
Current

Node disagreement loop

FlexDoc 3.5 names an undocumented runtime route, fails the default check, shows the contract gap beside the registration, and opens that route in the API Client.

  • A complete-discovery undocumented route fails flexdoc validate and names the method and path.
  • Acknowledgement keeps the route in the runtime record as informational and does not fail the check.
  • The finding opens the registered route. The request uses the snapshot origin, not an OpenAPI server the runtime never registered.
  • The client, backend, and CLI packages in this release are Apache-2.0.
FlexDoc 3.4
Released as 3.4.0

Hardening package release

FlexDoc 3.4.0 publishes the completed 3.3.x hardening stack. Package semver is independent of product-milestone labels.

  • Horizontally scaled Node host execution can share session state and partition admission.
  • Execution evidence uses the same vocabulary across the native executing runtimes.
  • Package versions and product-milestone labels are independent from this release onward.
FlexDoc 3.3
Released as 3.3.0

Backend Execution Expansion across native runtimes

FlexDoc 3.3 expands controlled API-host execution across supported native runtimes, so ordinary interactive API Client requests can run from the service network when a serving adapter advertises a real host executor while preserving the canonical request model.

  • Native execute routes now span Spring/JAX-RS, FastAPI/ASGI, Go, ASP.NET Core, Axum, Actix, Rack/Rails, Plug/Phoenix, Laravel and Symfony integrations when host execution is explicitly enabled and allowlisted.
  • Interactive API Client sends prefer an available API host by default, including hosts with capabilities: [], while reusable collection and headless execution remain direct by default unless host semantics are explicitly selected or required.
  • Exact-origin allowlists, metadata and link-local blocking, destination and redirect validation, bounded transport limits and explicit application auth/CSRF guidance keep backend-network execution capability-driven and fail-closed.
  • A permanent ten-runtime Host Impact baseline measures direct-versus-host latency, throughput, CPU/request, RSS/PSS and cooldown retention so the cost of running FlexDoc inside a service stays visible.
FlexDoc 3.2
Released as 3.2.0

Headless Runner for local and CI workflows

FlexDoc takes the canonical API Client request, script, test and collection model outside the browser with portable artifacts and flexdoc run, reusing the existing direct and backend-advertised host execution contracts instead of inventing a second request engine.

  • Export a saved request, folder subtree or collection as a portable, history-free Runner artifact with the selected environment and existing auth, variables and scripts intact.
  • flexdoc run executes through the same canonical request builder, collection ordering, variable resolution, inherited auth, scripts and tests used by the API Client.
  • Direct and existing advertised host execution are reported truthfully, with protected docs/execute authentication reusing --header, --bearer and --basic without leaking those credentials to direct targets.
  • Machine-readable run reports, stable per-item evidence, stop-on-failure and cancellation make collection runs practical in CI without creating a second History or Newman-compatible execution model.
FlexDoc 3.1
Released as 3.1.0

Backend-native Contract Validation

FlexDoc turns Runtime Intelligence into structured operation-level contract findings produced by the running Node backend, with the renderer and CLI consuming the same result.

  • Express, Fastify, Hono and NestJS produce backend-owned operation drift findings instead of relying on document-only validation.
  • Findings distinguish undocumented, unobserved, method-mismatched and verified duplicate operation registrations while preserving partial-discovery semantics.
  • Runtime Intelligence links documented findings back to OpenAPI operations and keeps route-presence fallback for compatible native snapshots.
  • flexdoc validate consumes the backend result in CI with JSON output, custom headers/auth and configurable failure thresholds.
FlexDoc 3.0
Released as 3.0.0

Runtime Intelligence and a better API workspace

FlexDoc can compare OpenAPI with routes registered by supported running frameworks. Try It and the API Client also share the same editor and scripting experience.

  • Runtime Intelligence shows matched, runtime-only and documented-only routes on supported backends.
  • Try It and the API Client share request editing, handoff state, command navigation and CodeMirror scripts.
  • Accessibility, responsive layouts and saved workspace preferences were tightened across the renderer.
  • Bundle size, large-spec rendering, caching, startup cost and memory use are measured in CI.
FlexDoc 2.9.9
Released as 2.9.9

Performance and production hardening

Added caching, ETags and repeatable performance checks for hosted documentation.

  • Node hosts cache generated docs pages and combine concurrent cold requests into one render.
  • Docs HTML supports deterministic ETag/304 revalidation while versioned renderer assets use long-lived caching.
  • CI tracks bundle size, large-spec rendering, startup time and memory use.
  • Static export remains available when you want no FlexDoc runtime work in the application.
FlexDoc 2.9.5
Released as 2.9.5

More REST body types and API-host execution

Added structured request bodies and server-side execution for requests that browser fetch cannot send.

  • URL-encoded, multipart, GraphQL and binary bodies work across editing, runs, import, History and replay.
  • Digest, Hawk, OAuth 1.0, AWS SigV4, NTLM intent and cookie API keys stay typed when imported or saved.
  • The Node backend can opt into cookie jars, configured mTLS certificates, Digest, Hawk, OAuth 1.0 and AWS SigV4.
  • Browser and host execution use the same response viewer, scripts, tests, History and collection runner.
FlexDoc 2.9
Released as 2.9.0

Collection runs, scripting help and History

Saved requests became repeatable workflows instead of isolated one-off calls.

  • Run collections and folders in saved order with progress, Stop and stop-on-failure controls.
  • Script IntelliSense adds completions, signatures, docs, variable keys and assertion help.
  • History adds search, grouped runs, response details, tests, logs, replay and deletion.
  • Send and collection runs use the same request, auth, variable, script and test logic.
FlexDoc 2.8
Released as 2.8.0

Postman import

Postman collections and environments can be imported into normal FlexDoc workspace data.

  • Import Postman Collection v2.1 requests, folders, variables, common auth, supported bodies and compatible scripts.
  • Import Postman environments into FlexDoc environments and keep them after reload.
  • Unsupported auth, script or body behavior is reported as a warning instead of being guessed.
  • Viewer settings and renderer options were also brought into the coordinated 2.8 release.
FlexDoc 2.7
Included in a later published release

Try It handoff and OAuth

Try It and the standalone API Client began sharing the same editable request state.

  • OpenAPI Try It can hand the live request directly into the API Client.
  • Inherited auth stays consistent across the handoff and saved request hierarchy.
  • Browser OAuth support expands beyond manually pasted access tokens.
FlexDoc 2.6
Included in a later published release

Persisted tests and script logs

Test results and script output became part of saved request History.

  • Post-response test results are saved with History entries.
  • Captured script output remains available after reload.
  • History keeps the validation context produced by the scripting runtime.
FlexDoc 2.5
Included in a later published release

Inherited auth and scripting

Shared authentication and script state reduced repeated setup across related requests.

  • Collection, folder and request auth follow an explicit inheritance chain.
  • OpenAPI authorization state carries into the API Client handoff.
  • OAuth access tokens and collection-variable scripting become reusable workspace features.
FlexDoc 2.4
Included in a later published release

Collection variables and nested folders

Collections gained the structure needed for larger reusable workspaces.

  • Collections can define reusable variables.
  • Folders can nest to arbitrary depth.
  • History replay keeps the request tied to its original collection.
FlexDoc 2.3
Released as 2.3.0

More backend frameworks

FlexDoc became available through native packages across the main backend ecosystems.

  • JavaScript/TypeScript hosts and native adapters use the same renderer contract.
  • .NET, JVM/Spring/JAX-RS, Python, PHP, Ruby, Go, Rust and Elixir gained native packaging or integrations.
  • Adapters serve local version-matched renderer assets instead of maintaining separate UI implementations.
FlexDoc 2.2
Released as 2.2.0

CLI, compatibility tests and API Client groundwork

The release added better validation, static docs tooling and the first pieces of the standalone API Client.

  • An OpenAPI compatibility corpus and browser regression tests define supported behavior.
  • The CLI can serve local docs and build self-contained static output.
  • Standalone API Client groundwork and Try It handoff started the broader workspace direction.
  • Prauga package migration and fingerprinted renderer assets made distribution more predictable.
FlexDoc 2.0
Released as 2.0.0

Shared renderer architecture

FlexDoc moved to one renderer and one OpenAPI/request model shared across frontend and backend integrations.

  • One browser renderer handles navigation, schemas, Try It, code samples and theming.
  • OpenAPI 3.0/3.1 parsing and request serialization moved into shared core logic.
  • Backend packages became thin hosts for the shared renderer instead of separate documentation products.
Versions

Downloads

Open the list when you need an older tag, its install command, source, docs or renderer archive.

Show all published versions15 releases

FlexDoc 3.5.0

Latest
September 22, 2026 · js/v3.5.0

FlexDoc 3.5 names an undocumented runtime route, fails the default check, shows the contract gap beside the registration, and opens that route in the API Client.

npm install @prauga/flexdoc-client@3.5.0 @prauga/flexdoc-backend@3.5.0
Release notes Docs Source Renderer Source .zip Source .tar.gz

FlexDoc 3.3.0

September 15, 2026 · js/v3.3.0

FlexDoc 3.3 expands controlled API-host execution across supported native runtimes, so ordinary interactive API Client requests can run from the service network when a serving adapter advertises a real host executor while preserving the canonical request model.

npm install @prauga/flexdoc-client@3.3.0 @prauga/flexdoc-backend@3.3.0
Release notes Docs Source Renderer Source .zip Source .tar.gz

FlexDoc 3.2.0

September 8, 2026 · js/v3.2.0

FlexDoc takes the canonical API Client request, script, test and collection model outside the browser with portable artifacts and flexdoc run, reusing the existing direct and backend-advertised host execution contracts instead of inventing a second request engine.

npm install @prauga/flexdoc-client@3.2.0 @prauga/flexdoc-backend@3.2.0
Release notes Docs Source Renderer Source .zip Source .tar.gz

FlexDoc 3.1.0

September 8, 2026 · js/v3.1.0

FlexDoc turns Runtime Intelligence into structured operation-level contract findings produced by the running Node backend, with the renderer and CLI consuming the same result.

npm install @prauga/flexdoc-client@3.1.0 @prauga/flexdoc-backend@3.1.0
Release notes Docs Source Renderer Source .zip Source .tar.gz

FlexDoc 3.0.0

September 7, 2026 · js/v3.0.0

FlexDoc can compare OpenAPI with routes registered by supported running frameworks. Try It and the API Client also share the same editor and scripting experience.

npm install @prauga/flexdoc-client@3.0.0 @prauga/flexdoc-backend@3.0.0
Release notes Docs Source Renderer Source .zip Source .tar.gz
Packages for FlexDoc 3.5

Package versions vary by ecosystem.

The JavaScript client and backend are 3.5.0. Native adapters keep their own semantic versions; the table below lists the versions that ship the current FlexDoc renderer.

Choose a framework
EcosystemPackageVersionRegistry / source
npm@prauga/flexdoc-client3.5.0Open
npm@prauga/flexdoc-backend3.5.0Open
npm@prauga/flexdoc-core0.5.2Open
npm@prauga/flexdoc-cli0.8.0Open
NuGetPrauga.FlexDoc.AspNetCore0.8.0Open
Mavencom.prauga.flexdoc:flexdoc-jvm0.11.0Open
Mavencom.prauga.flexdoc:flexdoc-jaxrs0.11.0Open
Mavencom.prauga.flexdoc:flexdoc-spring-boot-starter0.11.0Open
PyPIprauga-flexdoc0.9.0Open
Composerprauga/flexdoc0.5.0Open
RubyGemsprauga-flexdoc0.5.0Open
crates.ioprauga-flexdoc-host-execution0.2.0Open
crates.ioprauga-flexdoc-axum0.6.0Open
crates.ioprauga-flexdoc-actix0.5.0Open
Hexprauga_flexdoc0.5.0Open
Gogithub.com/prauga/flexdoc/adapters/go0.6.0Open
Looking for an older native package? GitHub Releases ↗ includes the ecosystem-specific Java, Python, .NET, Go, Rust, Ruby and Elixir tags.