Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36238
840ced2d fix(webpack): disable extractComments on the swc terser minimizer Production builds with `compiler: 'swc'` crashed during minification once terser-webpack-plugin resolved to 5.6.x: unknown field `extractComments`, expected one of `parse`, `compress`, `mangle`, ... terser-webpack-plugin 5.6 forwards the plugin-level `extractComments` option (default `true`) into @swc/core's minify options, which rejects it as an unknown field. The babel minimizer branch already set `extractComments: false`; the swc branch did not, so it inherited the crashing default. Set `extractComments: false` on the swc `TerserPlugin` to match the babel branch. On the previously pinned 5.3.x (which ignored the option) the emitted output is byte-identical, so this only removes the crash on 5.6+. Add a unit test asserting both minimizer branches set `extractComments: false`.
by Leosvel Pé...
Failed
36238
840ced2d fix(webpack): disable extractComments on the swc terser minimizer Production builds with `compiler: 'swc'` crashed during minification once terser-webpack-plugin resolved to 5.6.x: unknown field `extractComments`, expected one of `parse`, `compress`, `mangle`, ... terser-webpack-plugin 5.6 forwards the plugin-level `extractComments` option (default `true`) into @swc/core's minify options, which rejects it as an unknown field. The babel minimizer branch already set `extractComments: false`; the swc branch did not, so it inherited the crashing default. Set `extractComments: false` on the swc `TerserPlugin` to match the babel branch. On the previously pinned 5.3.x (which ignored the option) the emitted output is byte-identical, so this only removes the crash on 5.6+. Add a unit test asserting both minimizer branches set `extractComments: false`.
by Leosvel Pé...