Planned breaking changes for Rspack 2.0

[hardfist]

This topic is used to collect and discuss breaking changes planned for Rspack 2.0.

Please note that we do not have a clear timeline for Rspack 2.0 yet.

Example:

• remove RSPACK_CONFIG_VALIDATE environment variable and enable it by default

[chenjiahan]

Make @module-federation/runtime-tools optional

Currently, @module-federation/runtime-tools is a direct dependency of @rspack/core.

In Rspack 2.0 we can make it an optional peer dependency to reduce dependencies.

Context

Currently, Rspack's built-in @module-federation/runtime-tools is only used when using the MF 1.5 plugin and the implementation option is not set.

• If the application uses MF 2.0, only @module-federation/enhanced -> @module-federation/runtime-tools will be used:

devDependencies:
@module-federation/enhanced 0.14.0
└── @module-federation/runtime-tools 0.14.0
@rspack/core 1.2.8
└── @module-federation/runtime-tools 0.8.4  ---->  never used!

• If the application uses MF 1.0 or does not use MF, Rspack's built-in @module-federation/runtime-tools will never be used.

Benefit

By making @module-federation/runtime-tools optional, we can avoid installing unnecessary dependencies in the application and speed up the npm installation.

6 dependencies can be removed: