Your message dated Sat, 21 May 2022 23:22:56 +0530
with message-id <[email protected]>
and subject line Re: ReferenceError: options is not defined
has caused the Debian Bug report #993693,
regarding ReferenceError: options is not defined
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 [email protected]
immediately.)
--
993693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993693
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: webpack
Version: 5.6.0+~cs6.4.0-1~exp2
Severity: grave
I was trying to update another js-team package and couldn't understand
what was wrong until I tried to just run webpack by itself in another
directory:
$ webpack
[webpack-cli] ReferenceError: options is not defined
at Object.apply
(/usr/share/nodejs/webpack/lib/config/defaults.js:873:30)
at WebpackOptionsApply.process
(/usr/share/nodejs/webpack/lib/WebpackOptionsApply.js:453:16)
at createCompiler (/usr/share/nodejs/webpack/lib/webpack.js:78:28)
at create (/usr/share/nodejs/webpack/lib/webpack.js:115:15)
at webpack (/usr/share/nodejs/webpack/lib/webpack.js:123:46)
at f (/usr/share/nodejs/webpack/lib/index.js:35:15)
at WebpackCLI.createCompiler (/usr/share/nodejs/webpack-
cli/lib/webpack-cli.js:176:24)
at WebpackCLI.run (/usr/share/nodejs/webpack-cli/lib/webpack-
cli.js:268:25)
at async runCLI (/usr/share/nodejs/webpack-
cli/lib/bootstrap.js:59:9)
This means it's broken ; installing unstable's 4.43.0-6 made the error
go away, so it's a problem only with the new version.
Cheers,
J.Puydt
--- End Message ---
--- Begin Message ---
On Sat, 04 Sep 2021 23:13:50 +0200 Julien Puydt
<[email protected]> wrote:
> I was trying to update another js-team package and couldn't
understand
> what was wrong until I tried to just run webpack by itself in another
> directory:
This is an obsolete bug, this has since been fixed in newer versions in
experimental and now it is available in unstable.
--- End Message ---
