Why watch mode became a scheduling problem involving discovered dependencies, aggregated changes, stale builds, and a compiler that still rebuilt everything.

How Feopack exposed its compiler lifecycle to Rust and JavaScript plugins, then removed an abstraction that confused phases with hooks.

How Feopack added pitch, replaced noisy inline recipes with Meow v3, crossed the Rust/JavaScript boundary, and preserved one loader chain across two runtimes.

How Feopack's first text transform grew into a loader pipeline with rules, chained transforms, resource queries, virtual modules, and inline requests.

How Feopack grew from an empty Compilation into a module graph, one deliberately simple chunk, and a tiny runtime that could preserve basic ESM behavior.

Why Feopack began at the JavaScript boundary, how NAPI connected it to Rust, and what had to exist before the bundler could build its first module graph.

How Sui-Nebula-Analyzer uses NebulaGraph to model on-chain wallet relationships and power relationship queries, statistics, and visualization.