#Glossary

This glossary collects the most core and easily confused technical terms in the Esmx framework and micro-frontend architecture, helping users quickly understand the project architecture and technical concepts.

#Module Linking

Module Linking refers to the use of native ES Modules (ESM) and import maps to dynamically link multiple packages or modules at runtime, enabling decoupling and collaboration between them. This mechanism allows packages or modules to be independently developed, tested, and deployed, while being managed and loaded uniformly in the host application through import maps.

#Native ESM

Native ESM refers to the ES Modules mechanism natively supported by browsers and Node.js, allowing developers to use standard import/export syntax for modular development. All module linking and dependency isolation in the Esmx framework are implemented based on native ESM.

#import map

import map refers to a browser-native mechanism used to control the mapping of ESM module import paths. Through import maps, dependency isolation and multi-package collaboration can be achieved, preventing conflicts between packages.

#Zero Runtime

Zero Runtime refers to a framework that does not introduce any additional runtime code, with all functionality relying on native platform capabilities, thereby improving performance and reducing complexity.

#No Sandbox

No Sandbox refers to Esmx not relying on traditional sandbox mechanisms such as iframes for module isolation, but instead achieving security and isolation through native ESM and import maps, improving flexibility and performance.

#Dependency Isolation

Dependency Isolation refers to dependencies between modules or packages not interfering with each other. Esmx achieves dependency isolation through import maps and ESM, preventing conflicts between packages and ensuring system stability.

#Multi-Framework Integration

Multi-Framework Integration refers to Esmx supporting the integration and operation of multiple frontend frameworks (such as Vue, React, Svelte, etc.) within the same project, enabling collaborative development across multiple teams and technology stacks.

#Package Collaboration/Module Decoupling

Package Collaboration and Module Decoupling refer to packages or modules being able to be independently developed, tested, and deployed through the module linking mechanism, while working collaboratively at runtime to improve system maintainability and scalability.

#Micro Frontends

Micro Frontends refers to a frontend architecture pattern that allows multiple teams to independently develop, test, and deploy their respective frontend applications, which are then integrated into a whole through the host application. Esmx belongs to the micro-frontend architecture category.

#Host

Host refers to the core application in a micro-frontend or module linking architecture that is responsible for loading, integrating, and orchestrating remote applications or modules. The host application typically handles global routing, state management, and UI frameworks.

#Remote Application/Module

Remote Application/Module refers to independent sub-applications or functional modules that are dynamically loaded and integrated by the host application, supporting independent development, testing, and deployment.

#Application

Application refers to a frontend subsystem that can run and be deployed independently, typically containing complete pages, routing, and business logic.

#Module

Module refers to a functional unit that can be linked and reused, such as packages, component libraries, utility libraries, etc. It is the foundation for achieving decoupling and reuse in Esmx.

#Package

Package refers to NPM packages or Monorepo sub-packages, emphasizing physical structure and publishing units, and is the foundation for multi-package collaboration in Esmx.