Your message dated Sat, 21 May 2022 23:06:11 +0530
with message-id <b8u8cr.cewhop9jom...@onenetbeyond.org>
and subject line Re: webpack 5 unusable: TypeError: this.program.configureOutput
has caused the Debian Bug report #1002494,
regarding webpack 5 unusable: TypeError: this.program.configureOutput
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1002494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: webpack
Version: 5.65.0+dfsg+~cs9.20.9-1
Severity: grave
Justification: renders package unusable
When trying to use webpack5, I got the following error:
make[1]: Entering directory '/<<PKGBUILDDIR>>'
webpack --mode production
(node:647989) UnhandledPromiseRejectionWarning: TypeError:
this.program.configureOutput is not a function
at new WebpackCLI (/usr/share/nodejs/webpack-cli/lib/webpack-cli.js:19:18)
at runCLI (/usr/share/nodejs/webpack-cli/lib/bootstrap.js:5:15)
at Object.<anonymous> (/usr/share/nodejs/webpack-cli/bin/cli.js:17:1)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at runCli (/usr/share/nodejs/webpack/bin/webpack.js:69:2)
(node:647989) UnhandledPromiseRejectionWarning: Unhandled promise rejection.
This error originated either by throwing inside of an async function without a
catch block, or by rejecting a promise which was not handled with .catch(). To
terminate the node process on unhandled promise rejection, use the CLI flag
`--unhandled-rejections=strict` (see
https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id:
1)
(node:647989) [DEP0018] DeprecationWarning: Unhandled promise rejections are
deprecated. In the future, promise rejections that are not handled will
terminate the Node.js process with a non-zero exit code.
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
By the way at least to dependencies are missing:
* node-execa
* node-import-local (provided by node-jest-bundle)
Cheers,
Yadd
--- End Message ---
--- Begin Message ---
On Thu, 23 Dec 2021 09:51:27 +0100 Yadd <y...@debian.org> wrote:
> When trying to use webpack5, I got the following error:
>
This looks like an obsolete bug report.
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> webpack --mode production
> (node:647989) UnhandledPromiseRejectionWarning: TypeError:
this.program.configureOutput is not a function
> By the way at least to dependencies are missing:
> * node-execa
> * node-import-local (provided by node-jest-bundle)
node-import-local dependency was added in a recent upload.
--- End Message ---
