On 2/4/22 3:45 PM, Jonas Smedegaard wrote:
Hi Caleb, Quoting Caleb Adepitan (2022-02-04 08:46:29)I just arrived at a working patch for terser-webpack-plugin to circumvent breaking changes in node-terser 5 which is required by the package. The available version of node-terser in debian is 4 which is behind the terser package upstream. This patch is an ad-hoc fix for the bug pending the node-terser package is updated to a compatible version.This _relates_ to NodeJS module terser, but is it most specifically tied to terser, webpack, or terser-webpack-plugin? You post the above to bug#1004471 which is tied to Debian package node-terser, but your presented patch seems not for terser but for something else - webpack or terser-webpack-plugin. Helpful if you can clarify further what fixes what (not only for what end goal). - Jonas
Hi Jonas,This affects terser-webpack-plugin which affects webpack 5. This patch relates to *terser-webpack-plugin* (not terser itself) to circumvent breaking changes in terser 5. The current terser-webpack-plugin has been adapted to use terser 5 while the version available to it is terser 4.
The patch makes sure terser 4 continues to work with the package while not preventing terser 5 also.
Thanks!
OpenPGP_0x8A1B2CC96775D2D7.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature