[Pkg-javascript-devel] Bug#911338: Bug#911338: node-webpack: new upstream version 4.21.0 available

[Pirate Praveen]

On 2018, ഒക്‌ടോബർ 19 1:00:05 AM IST, Daniel Kahn Gillmor <dkg at fifthhorseman.net> wrote:
>Source: node-webpack
>Version: 3.5.6-3
>Severity: wishlist
>Control: affects -1 src:gpgme1.0
>Control: block 911189 by -1
>
>https://github.com/webpack/webpack/archive/v4.21.0.tar.gz is available
>upstream.
>
>The debian package for webpack has not been updated since 2018-03-08.
>
>I'm trying to use webpack to build the GPGME javascript bindings (see
>https://bugs.debian.org/911189), and that package uses webpack to
>bundle its javascript.
>
>but when i try to build it using the "webpack" binary in unstable, i
>see errors like so:
>
>-----------
>0 dkg at sid:~/src/gpgme/gpgme/lang/js$ npx webpack --config
>webpack.conf_unittests.js 
>Invalid configuration object. Webpack has been initialised using a
>configuration object that does not match the API schema.
>- configuration has an unknown property 'mode'. These properties are
>valid:
>object { amd?, bail?, cache?, context?, dependencies?, devServer?,
>devtool?, entry, externals?, loader?, module?, name?, node?, output?,
>parallelism?, performance?, plugins?, profile?, recordsInputPath?,
>recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?,
>target?, watch?, watchOptions? }
>   For typos: please correct them.
>For loader options: webpack 2 no longer allows custom properties in
>configuration.
>Loaders should be updated to allow passing options via loader options
>in module.rules.
>Until loaders are updated one can use the LoaderOptionsPlugin to pass
>these options to the loader:
>     plugins: [
>       new webpack.LoaderOptionsPlugin({
>         // test: /\.xxx$/, // may apply this only for some modules
>         options: {
>           mode: ...
>         }
>       })
>     ]
>1 dkg at sid:~/src/gpgme/gpgme/lang/js$ 
>-----------
>
>I suspect this is due to webpack being out of date in debian unstable.
>
>(I can comment out the offending "mode: 'production'" lines from
>webpack.conf.js as a workaround, but it looks like upstream expects a
>modern version of webpack)
>
>Thanks for maintaining webpack in debian!

The easiest option would be to adapt configuration for webpack 3. I briefly looked into updating webpack to 4 and it will require updating babel to 7 as well. If there is more people interested in helping I can join them else I will wait till more packages need webpack 4.

My main motivation in packaging webpack was gitlab. Even though it wants webpack 4, I have to package a lot more dependencies before I can use packaged versions (currently gitlab is in contrib as I pull the dependencies from npmjs.com in postinst). So my webpack 4 need is not urgent, but if more people join I can work on it.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.