Runtime Package Delivery

M7 Bootstrap

Package loading, mounting, and teardown for runtime-delivered modules, assets, and features. It keeps bootstrap glue out of page scripts and gives teams a dependency-aware way to stage UI pieces on demand.

Discuss Bootstrap Adoption See m7.js Library View GitHub Repo
Dependency-aware Mount / unmount Package registry Backend-agnostic

Overview

M7 Bootstrap is a runtime package management toolkit for loading, mounting, and unloading packages in dynamic JavaScript environments. It abstracts away the complexity of fetching, integrating, and organizing assets and modules, so product code can focus on behavior instead of plumbing.

Because it is written entirely in JavaScript, it stays backend-agnostic and can run in browsers, Node.js, Electron, or any JS runtime that supports ES modules. You do not need special server-side infrastructure beyond serving the package files.

Why Teams Use It

  • Move repetitive bootstrap logic out of page scripts.
  • Load dashboards, demos, plugins, and internal tools on demand.
  • Keep runtime growth controlled with clear load and teardown behavior.
  • Support legacy augmentation and package-based delivery without a framework migration.

The real value is controlled runtime composition. M7 Bootstrap keeps package delivery explicit, which means teams can grow a product surface without turning every page into one-off loader code.

How It Works

  1. Resolve package definitions from URLs, repo references, or inline definitions.
  2. Fetch dependent packages and supporting modules in the right order.
  3. Stage assets and modules into the runtime registry.
  4. Mount concrete DOM assets with package-scoped lifecycle hooks.
  5. Unload packages later and clean up assets and modules when you are done.

The package loader is dependency-aware, the mount manager is explicit, and the unload path is designed to keep teardown predictable.

How It Fits With m7.js

m7.js provides shared runtime primitives, Active Tags handles workflow-oriented UI behavior, and M7 Bootstrap is the delivery layer that can pull those pieces into a page on demand.

In practice, that means you can keep utility code, runtime behavior, and package delivery separated without losing the ability to combine them at runtime.

Delivery

Start with the repo and quick start guide if you want the implementation details and setup flow.

For teams with runtime-delivered UI, package-based composition usually beats bespoke bootstrap code. M7 Bootstrap is the layer that makes that practical.