Feature Parity Table

[BioPhoton]

It would be good to have a feature parity table present in the repository.

Related issues:

• [Rspack] Known Issues - Feature Parity #7
• Documenting known issues and missing features #79

We should decide:

• where to put this information
• what to compare
• what not to compare and how to communicate it
• how to link benchmarks

Suggested solution

We need a comparisin on package level. Is should be visible in the docs app as well as main readme.

Acceptance Criteria

• The information should cover the comparison approach as well as detailed table - docs: start feature parity section #110
• The information is visible in the main README.md - docs: start feature parity section #110
• The information is visible in the docs app -
• Check related issues if we can add something to the table
• polish table, remove incorrect rows

[Coly010]

It would be nice if this could be diffed 😅

In terms of overall where this should go, I think in 2 places for now:

• Root README.md
• Docs application - Potentially on the homepage - or in a separate comparison doc

This portion about Rsbuild being a drop-in replacement for Webpack is incorrect. That would make sense in the Rspack section.

Module Federation for Rspack is also stable. Rsbuild also supports Module Federation.

[BioPhoton]

It would be nice if this could be diffed 😅

here the diff: #110

[JeanMeche]

Few items I have in mind that the CLI supports and that might be worth mentionning:

One feature I have in mind that the CLI handles, is automatic downleveling via browserslist / esbuild target.

example: https://esbuild.github.io/try/#dAAwLjE5LjExAC0tdGFyZ2V0PXNhZmFyaTEzAGNvbnN0IGEgPSAoTWF0aC5yYW5kKCkgPiAwLjUgPyAxIDogdW5kZWZpbmVkKSA/PyAzOw

[JeanMeche]

The CLI has a set of flags that can be usefull:

https://github.com/angular/angular-cli/blob/92aa9e05bb46f3373b69529b22c56bb2dce3834f/packages/angular_devkit/build_angular/src/utils/environment-options.ts#L61

It find myself very often using NG_BUILD_MANGLE=0 to build a prod app with all optimization BUT without mangling for example.

[JeanMeche]

How does the stack handle TS ?

TS can be feeded directly to esbuild, which could enable some optimization with isolatedModules: true, see https://blog.angular.dev/using-isolatedmodules-in-angular-18-2-68a7d3a6c03d

[Coly010]

How does the stack handle TS ?

TS can be feeded directly to esbuild, which could enable some optimization with isolatedModules: true, see https://blog.angular.dev/using-isolatedmodules-in-angular-18-2-68a7d3a6c03d

If isolated modules is set to true, and the file contains no angular transformations, the TS is fed to Rspack’s builtin swc-loader individually to be transformed.

[Coly010]

The CLI has a set of flags that can be usefull:

https://github.com/angular/angular-cli/blob/92aa9e05bb46f3373b69529b22c56bb2dce3834f/packages/angular_devkit/build_angular/src/utils/environment-options.ts#L61

It find myself very often using NG_BUILD_MANGLE=0 to build a prod app with all optimization BUT without mangling for example.

Fair comparison. There is currently no method to override the default swc options.

[Coly010]

Few items I have in mind that the CLI supports and that might be worth mentionning:

One feature I have in mind that the CLI handles, is automatic downleveling via browserslist / esbuild target.

example: https://esbuild.github.io/try/#dAAwLjE5LjExAC0tdGFyZ2V0PXNhZmFyaTEzAGNvbnN0IGEgPSAoTWF0aC5yYW5kKCkgPiAwLjUgPyAxIDogdW5kZWZpbmVkKSA/PyAzOw

Currently unhandled but very easy to support: https://rspack.dev/config/target#browserslist

[BioPhoton]

@JeanMeche How do you feel about the content of this list? IMO the first thing we can align on is the package mapping and then we can group features.

[JeanMeche]

@angular-devkit/build-angular is being replaced by @angular/build (to help dropping the webpack dependency

@angular/compiler contains the compiler itself, I don't think its the equivalent here. I would need to check what ng-rspack-compiler actually does (but its probably @angular/build too)

[Coly010]

@angular-devkit/build-angular is being replaced by @angular/build (to help dropping the webpack dependency

@angular/compiler contains the compiler itself, I don't think its the equivalent here. I would need to check what ng-rspack-compiler actually does (but its probably @angular/build too)

Yes it would be. It uses abstractions from the @angular/build package.