Pitfalls and checklist

Pitfalls and checklist Common mistakes Destructuring a sibling during assembly const { database } = services; // undefined if database is built later Access it inside a method instead. await in a factory Factories and the assemble callback must be synchronous. Move asynchronous work to onInit . Forgetting await init(...) Creators do not run hooks. Without init, pools stay closed. Numeric factory keys { 2: a, 1: b } is iterated as 1, 2 by JavaScript. Use names. Two onInit in one object The second silently replaces the first. Treating internal as security It is a type-level convention only. The value is present at runtime. Infinite recursion through deferred cycles Deferred circular references are safe to build, but circular calls still recurse forever. Before you ship Factories are synchronous and return values directly. Siblings are accessed inside functions, not at construction time. Consuming layers type their arguments as PublicLayer<\dots> . init is called per layer, lowest first. dispose is called in the reverse order. Each object has at most one onInit and one onDispose . Can one factory depend on a later one? Only through deferred access. Either reorder the definitions or touch the other component inside a function. Is there a global container? No. Each creator call builds a new, independent container.