Guide
API
Blog
Guide
API
Blog

Environmental Requirements

This document outlines the environmental requirements for using this framework, including Node.js environment and browser compatibility.

Node.js Environment

The framework requires Node.js version >= 24, primarily to support TypeScript type imports (via the --experimental-strip-types flag) without additional compilation steps.

Browser Compatibility

The framework defaults to compatibility mode builds to support a wider range of browsers. However, note that to achieve full browser compatibility support, you need to manually add the es-module-shims dependency.

Compatibility Mode (Default)

BrowserMinimum Version
🌐 Chrome>= 64
🌊 Edge>= 79
🦊 Firefox>= 67
🧭 Safari>= 11.1

Compatibility mode requires browsers to support both Dynamic Import and import.meta features.

According to Can I Use statistics, browser coverage in compatibility mode reaches 95.59%.

Native Support Mode

BrowserMinimum Version
🌐 Chrome>= 89
🌊 Edge>= 89
🦊 Firefox>= 108
🧭 Safari>= 16.4

Native support mode offers the following advantages:

  1. Zero runtime overhead, no additional module loader required
  2. Native browser parsing for faster execution
  3. Better code splitting and on-demand loading capabilities

According to Can I Use statistics, browser coverage in native support mode reaches 93.5%.

Enabling Compatibility Support

Important Note

While the framework defaults to compatibility mode builds, to achieve full support for older browsers, you need to add the es-module-shims dependency to your project.

Add the following script to your HTML file:

<!-- Development environment -->
<script async src="https://ga.jspm.io/npm:[email protected]/dist/es-module-shims.js"></script>

<!-- Production environment -->
<script async src="/path/to/es-module-shims.js"></script>
Best Practices
  1. Production environment recommendations:
    • Deploy es-module-shims to your own server
    • Ensure resource loading stability and access speed
    • Avoid potential security risks
  2. Performance considerations:
    • Compatibility mode introduces minor performance overhead
    • Decision to enable can be based on target user base's browser distribution