You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/docs/en/blog/v1-0.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ Rslib is a library development tool based on [Rsbuild](https://rsbuild.rs/) and
30
30
The ecosystem already offers many library build tools that compile JavaScript and TypeScript and produce common output formats. Rslib builds on this foundation by bringing mature application build capabilities and ecosystem support to library development. Its key advantages include:
31
31
32
32
-**Supports multiple distribution options, including Module Federation**: Rslib can produce ESM and CJS output that is loaded directly by Node.js or processed further by downstream build tools. It can also generate UMD and IIFE output that browsers load directly through `<script>` tags. For cross-application runtime module loading, Rslib can also generate Module Federation output and provide support for local development and integration workflows.
33
-
-**Keeps pace with evolving languages, frameworks, and standards**: Rslib actively follows advances in TypeScript, framework ecosystems, TC39 proposals, and web standards. For example, Rslib supports generating declaration files with TypeScript 7, enabling React Compiler, and importing non-JavaScript modules and assets using Import Attributes, WebAssembly ESM Integration, and Source Phase Imports.
33
+
-**Keeps pace with evolving languages, frameworks, and standards**: Rslib actively follows advances in TypeScript, framework ecosystems, TC39 proposals, and web standards. For example, Rslib supports generating declaration files with TypeScript 7, enabling React Compiler, and importing non-JavaScript modules and assets using [Import Attributes](https://github.com/tc39/proposal-import-attributes), [WebAssembly ESM Integration](https://github.com/WebAssembly/esm-integration), and [Source Phase Imports](https://github.com/tc39/proposal-source-phase-imports).
34
34
-**Builds on the Rspack and webpack ecosystems**: Rslib can use Rsbuild plugins as well as many plugins and loaders from the Rspack and webpack ecosystems. Developers can continue applying the knowledge and experience they have gained from these ecosystems to library development. When applications also use Rsbuild or Rspack, they can share common configurations and plugins with library projects, reducing duplicate maintenance.
35
35
36
36
## From 0.x to 1.0 \{#from-v0-to-v1}
@@ -57,7 +57,7 @@ A single configuration file can define multiple outputs, each with its own [form
57
57
58
58
Rslib places particular emphasis on ESM output. It generates ESM output that is designed for static analysis and supports code splitting, making it easier for downstream build tools to perform tree shaking and further processing. Rslib also optimizes the default handling of external dependencies in ESM output, preserving module-loading semantics from the source code more accurately and reducing behavioral differences introduced by build transformations.
59
59
60
-
In addition to common module formats, Rslib offers an experimental [executable generation](/config/lib/experiments#experimentsexe) capability. This feature is based on Node.js SEA and currently supports a single bundled entry targeting Node.js. The generated executable can run on target systems where Node.js is not installed, making it suitable for distributing CLIs and other Node.js programs.
60
+
In addition to common module formats, Rslib offers an experimental [executable generation](/config/lib/experiments#experimentsexe) capability. This feature is based on [Node.js SEA](https://nodejs.org/api/single-executable-applications.html) and currently supports a single bundled entry targeting Node.js. The generated executable can run on target systems where Node.js is not installed, making it suitable for distributing CLIs and other Node.js programs.
0 commit comments