npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@fictjs/runtime

v0.15.0

Published

Fict reactive runtime

Readme

@fictjs/runtime

Node CI npm license

Fict reactive runtime

Usage

npm install @fictjs/runtime
# or
yarn add @fictjs/runtime

You can visit Fict for more documentation.

Dev/Prod Mode Contract (__DEV__)

Runtime dev-only branches use this precedence:

  1. __DEV__ (recommended, compile-time constant)
  2. Fallback: process.env.NODE_ENV !== 'production' when process exists

For browser builds, define __DEV__ explicitly in your bundler for predictable DX and dead-code elimination:

  • development: __DEV__ = true
  • production: __DEV__ = false

Multi-Document Contract (iframe / foreign Document)

@fictjs/runtime supports rendering into containers owned by non-global documents (for example, elements from an iframe document). Runtime-created nodes, markers, and fragments are created from the active ownerDocument.

Supported contract:

  • render() into a container from another Document
  • list/conditional/suspense marker creation in that container's ownerDocument
  • node insertion paths that rely on runtime-created nodes

Important caveat:

  • If user code manually returns nodes created from a different document and inserts them into another document tree, runtime may fall back to adoptNode() or importNode() during insertion/reordering. importNode() clones DOM nodes and does not preserve JS-side expando state or imperative listeners attached outside of Fict's binding flow.

Recommendation:

  • Create DOM nodes using the target container's ownerDocument (or let Fict create nodes) when working across iframe/foreign-document boundaries.

Runtime Stability Stress

Run stress scenarios for runtime correctness and reliability:

pnpm --dir packages/runtime test:stress

Long profile:

pnpm --dir packages/runtime test:stress:long

Root aliases are also available:

pnpm stress:runtime
pnpm stress:runtime:long

Environment knobs:

  • FICT_RUNTIME_SOAK_ITERS
  • FICT_RUNTIME_CHURN_CYCLES
  • FICT_RUNTIME_CHURN_LIST_SIZE
  • FICT_RUNTIME_LEAK_ROUNDS
  • FICT_RUNTIME_LEAK_EFFECTS_PER_ROUND
  • FICT_RUNTIME_MAX_HEAP_GROWTH_BYTES
  • FICT_RUNTIME_BACKPRESSURE_UPDATES
  • FICT_RUNTIME_BACKPRESSURE_TIMEOUT_MS
  • FICT_RUNTIME_MAX_DRAIN_LATENCY_MS