[Pkg-javascript-devel] node-jschardet: RFS for bug 1003336 (webpack5)
Hi, I just updated node-jschardet to resolve issues with webpack5 build as reported earlier here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003336 The updated package is located at https://salsa.debian.org/calebpitan/node-jschardet Thanks! OpenPGP_0x8A1B2CC96775D2D7.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-clipboard: RFS for Bug 1003333 (webpack5)
Hi, I just updated node-clipboard to resolve issues with webpack5 build as reported earlier here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=100 The updated package is located at https://salsa.debian.org/calebpitan/node-clipboard Thanks! OpenPGP_0x8A1B2CC96775D2D7.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1003332: Proposed webpack5 compatible patch for node-es6-promise.
Hi, I just updated my fork of node-es6-promise which was reported to fail build with webpack5 earlier. I've looked into the problem and found out from the error log that the '--output' option has been dropped in webpack5 in favor of '--output-filename' and '--output-path'. I have made changes in the build script in debian/rules accordingly to fix this issue. Ordinarily one would think changing '--output' to '--output-filename' fixes it, only to find out soon that it spirals another problem with the terser minifier script. A Node.js ENOENT exception is thrown because '--output-filename dest-web/es6-promise.js' won't create directory 'dest-web' till you split it into '--output-path dest-web --output-filename es6-promise.js' which makes sure that if 'dest-web' doesn't exist, it will be created. Here's is a link to my patch on salsa https://salsa.debian.org/calebpitan/node-es6-promise/-/commit/12990ea0b29c1258dedca858e76328ee7fc6e064.patch I've run the builds with webpack5 and have made sure build passes Cheers, Caleb Adepitan OpenPGP_0x8A1B2CC96775D2D7.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] RFS: node-esprima
On 2/16/22 6:16 AM, Yadd wrote: On 15/02/2022 18:44, Caleb Adepitan wrote: Hello, I just updated node-esprima which was some time ago reported to have failed build with webpack 5. We've fixed issue with webpack 5 and I've also updated node-esprima as needed. I've made sure it builds successfully and passes tests including autopkgtest tests. Here is the repo that has the changes: https://salsa.debian.org/calebpitan/node-esprima I'd love to request for sponsorship and uploading. Thanks, Caleb Adepitan. Here is the changelog. * first: 4.0.1+ds+~4.0.3-3 wasn't pushed (to NEW) So should I keep this version rather than bumping the revision to 4? * second: I don't see any change related to webpack5 Turns out node-esprima wasn't buggy. It was webpack 5 all along, so node-esprima doesn't need any changes related to webpack 5 as it builds fine. The only problem with node-esprima was the missing files which I tried adding to debian/node-esprima.install. Do you think I should report the missing files as a bug in node-esprima, probably for historical purpose, although this changes fixes it? --- node-esprima (4.0.1+ds+~4.0.3-4) experimental; urgency=medium * Team upload. * Add all missing files -- Caleb Adepitan Tue, 15 Feb 2022 18:24:57 +0100 node-esprima (4.0.1+ds+~4.0.3-3) experimental; urgency=medium * Team upload * Split libjs-esprima to own package * Build doc -- Bastien Roucariès Tue, 05 Oct 2021 09:10:18 + OpenPGP_0x8A1B2CC96775D2D7.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] RFS: webpack 5 (experimental)
On 2/16/22 6:05 AM, Yadd wrote: On 15/02/2022 19:25, Caleb A. wrote: It's done https://salsa.debian.org/calebpitan/node-webpack/-/tree/master-5 <https://salsa.debian.org/calebpitan/node-webpack/-/tree/master-5> Thanks! Hi, I don't see any changes Updated to this: --- a/debian/changelog +++ b/debian/changelog @@ -1,17 +1,13 @@ node-webpack (5.65.0+dfsg+~cs9.20.9-3) experimental; urgency=medium * Team upload. + * Apply version constraint to node-commander * Patch terser-webpack-plugin to circumvent breaking change in dependency, node-terser * Update control file + * Update salsa-ci.yml to build on experimental + * Update changelog - -- Caleb Adepitan Tue, 15 Feb 2022 19:05:41 +0100 - -node-webpack (5.65.0+dfsg+~cs9.20.9-3) experimental; urgency=medium - - * Team upload. - * Apply version constraint to node-commander - - -- Caleb Adepitan Sat, 15 Jan 2022 08:14:47 +0100 + -- Caleb Adepitan Wed, 16 Feb 2022 08:32:05 +0100 https://salsa.debian.org/calebpitan/node-webpack/-/tree/master-5 Better now, I think. On Tue, 15 Feb 2022 at 18:49, Caleb A. <mailto:calebpi...@gmail.com>> wrote: Okay will do that and let you know when it’s done. On Thu, 10 Feb 2022 at 18:06, Yadd mailto:y...@debian.org>> wrote: On 10/02/2022 17:02, Caleb A. wrote: > Hello, > > I've made some changes in webpack 5 and would like that it be revised to > make sure it's safe for sponsorship and uploading to experimental. > > Here: https://salsa.debian.org/calebpitan/node-webpack > <https://salsa.debian.org/calebpitan/node-webpack> > > Thanks, > > Caleb Adepitan. Hi, which branch, master-5 ? If yes, please update debian/changelog: some changes aren't documented. Cheers, Yadd OpenPGP_0x8A1B2CC96775D2D7.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] RFS: node-esprima
Hello, I just updated node-esprima which was some time ago reported to have failed build with webpack 5. We've fixed issue with webpack 5 and I've also updated node-esprima as needed. I've made sure it builds successfully and passes tests including autopkgtest tests. Here is the repo that has the changes: https://salsa.debian.org/calebpitan/node-esprima I'd love to request for sponsorship and uploading. Thanks, Caleb Adepitan. OpenPGP_0x8A1B2CC96775D2D7.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] RFS: webpack 5 (experimental)
Hello, I've made some changes in webpack 5 and would like that it be revised to make sure it's safe for sponsorship and uploading to experimental. Here: https://salsa.debian.org/calebpitan/node-webpack Thanks, Caleb Adepitan. OpenPGP_0x8A1B2CC96775D2D7.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1004471: Bug#1004471: Pending patch for terser-webpack-plugin in webpack 5 till a new upstream for node-terser is uploaded
Sorry for the confusion I've caused. I was hoping mentioning that "terser-webpack-plugin embedded in webpack package" in the initial wishlist bug report (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004471) stays relevant in subsequent discussions under the report. I probably shouldn't have shared a patch intended for node-webpack (terser-webpack-plugin) under a bug filed for node-terser. I only thought since the report mentioned that the bug affects webpack it would be fine to add some additional info about a pending patch to affected packages till the node-terser package is updated. It might help to later know that when node-terser gets updated and the wishlist bug is closed, the patch should become irrelevant and be removed from the affected package. The patch intended no changes to node-terser, only the packages affected by an incompatible version of node-terser which as I mentioned was terser-webpack-plugin embedded in webpack 5. The only changes intended for node-terser package as mentioned by the wishlist bug is to update node-terser to latest upstream, terser 5. Thanks for taking the time, Caleb On 2/5/22 4:04 PM, Jonas Smedegaard wrote: Quoting Caleb Adepitan (2022-02-05 11:42:51) On 2/4/22 3:45 PM, Jonas Smedegaard wrote: 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). [...] 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. You continue to talk about some mysterious "terser-webpack-plugin" which I fail to locate in Debian, and you do that in a bugreport targeted "terser". Do you see how that is confusing? After some investigation (which I had hoped you would have avoided by clarifying for me), I discovered that "terser-webpack-plugin" is embedded in the Debian package "webpackage". I have now filed bug#1005017 regarding the lack of proper hinting about that embedded project. Not your fault that webpack is a mess, but would have helped regardless if you had mentioned from a *Debian* viewpoint what you were working on (not only from an NPM viewpoint). Please, if you want some changes done to the Debian package "terser" then clarify what that action is (I don't recognize from the previously attached patch what action for the **ter** package is requested). Please, if instead you intent no changes for the "terser" package, just want to notify about progress elsewhere in the stack, then clarify that. Kind regards, and thanks for your work, - Jonas OpenPGP_0x8A1B2CC96775D2D7.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1004471: Bug#1004471: Pending patch for terser-webpack-plugin in webpack 5 till a new upstream for node-terser is uploaded
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 -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1004471: Pending patch for terser-webpack-plugin in webpack 5 till a new upstream for node-terser is uploaded
Hi,
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.
Here is the proposed patch:
https://salsa.debian.org/calebpitan/node-webpack/-/commit/208febe14d117dc134543fd9773c8eca02d1d68c.patch
--- a/terser-webpack-plugin/src/utils.js
+++ b/terser-webpack-plugin/src/utils.js
@@ -264,8 +264,11 @@ async function terserMinify(
// Let terser generate a SourceMap
if (sourceMap) {
-// @ts-ignore
-terserOptions.sourceMap = { asObject: true };
+const pkg = require("terser/package.json")
+if (parseInt(pkg.version) > 4) {
+ // @ts-ignore
+ terserOptions.sourceMap = { asObject: true };
+}
}
/** @type {ExtractedComments} */
@@ -284,7 +287,11 @@ async function terserMinify(
}
const [[filename, code]] = Object.entries(input);
- const result = await minify({ [filename]: code }, terserOptions);
+ let result = minify({ [filename]: code }, terserOptions);
+
+ if (result instanceof Promise) {
+result = await result
+ }
return {
code: /** @type {string} **/ (result.code),
OpenPGP_0x8A1B2CC96775D2D7.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1004471: Update node-terser to latest upstream (node-terser 5)
Source: node-terser Version: 4.8.0-1 Severity: wishlist User: pkg-javascript-devel@alioth-lists.debian.net Usertags: webpack5 Update node-terser to v5 which is required by terser-webpack-plugin embededded in the webpack package. The current version of node-terser breaks terser-webpack-plugin and consequently, webpack 5 due to breaking changes in node-terser. Thanks, Caleb Adepitan OpenPGP_0x8A1B2CC96775D2D7.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1003260: leaflet-image: FTBFS with webpack5: Invalid configuration object
Hi Jonas, Concerning the bug report where leaflet-image build with webpack 5 breaks due to an invalid configuration object, the major problem wasn't from the configuration object, but the `-d` option passed in build script in `debian/rules` which specifies a devtool option that has become "more strict" in webpack 5. This option passed in the build script overrides that in the config file. The `node` option targeted to mock Node.js fs module with an empty object is also no longer relevant. See https://webpack.js.org/configuration/resolve/#resolvefallback Here's a patch that shows my changes: https://salsa.debian.org/calebpitan/leaflet-image/-/commit/ff6837954c29706d5154c9d9abb54f92ad0171b2.patch OpenPGP_0x8A1B2CC96775D2D7.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] RFS: leaflet-image
Hi there, I just updated the leaflet-image package from 0.4.0~dfsg-4 to 0.4.0~dfsg-5. Which fixes one of the bugs encountered when reverse building with webpack 5. Here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003260. I would like you to confirm if it's safe for sponsorship and uploading https://salsa.debian.org/calebpitan/leaflet-image Thanks! Caleb Adepitan OpenPGP_0x8A1B2CC96775D2D7.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1003946: node-fuzzaldrin-plus: FTBFS with webpack 5: Could not find *.dsc
Source: node-fuzzaldrin-plus Version: 0.4.5+repack10+~cs71.23.57-2 Severity: important Tags: ftbfs User: pkg-javascript-devel@alioth-lists.debian.net Usertags: webpack5 Hi, We are starting to build against webpack5 in experimental and the package needed for local build is webpack and node-webpack-source from experimental. During a test rebuild, node-fuzzaldrin-plus was found to fail to build in that situation. Relevant part (hopefully): +--+ | Fetch source files | +--+ E: Could not find *.dsc +--+ | Cleanup | +--+ Purging /build/*.dsc-3nkpX5 Not cleaning session: cloned chroot in use E: Failed to fetch source files The full log is attached to this mail. sbuild (Debian sbuild) 0.81.2 (31 January 2021) on debian +==+ | *.dsc (amd64)Tue, 18 Jan 2022 11:29:04 + | +==+ Package: *.dsc Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: binary I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-d7b56ab8-038d-4ebd-ba69-be093f4ab494' with '<>' W: ../webpack_5.65.0+dfsg+~cs9.20.9-3_all.deb is neither a regular file nor a directory. Skipping... I: NOTICE: Log filtering will replace 'build/*.dsc-3nkpX5/resolver-UZZdyD' with '<>' +--+ | Update chroot| +--+ Get:1 file:/build/*.dsc-3nkpX5/resolver-IramXe/apt_archive ./ InRelease Ign:1 file:/build/*.dsc-3nkpX5/resolver-IramXe/apt_archive ./ InRelease Get:2 file:/build/*.dsc-3nkpX5/resolver-IramXe/apt_archive ./ Release [951 B] Get:2 file:/build/*.dsc-3nkpX5/resolver-IramXe/apt_archive ./ Release [951 B] Get:3 file:/build/*.dsc-3nkpX5/resolver-IramXe/apt_archive ./ Release.gpg Ign:3 file:/build/*.dsc-3nkpX5/resolver-IramXe/apt_archive ./ Release.gpg Get:4 file:/build/*.dsc-3nkpX5/resolver-IramXe/apt_archive ./ Packages [807 B] Err:4 file:/build/*.dsc-3nkpX5/resolver-IramXe/apt_archive ./ Packages Could not open file /build/*.dsc-3nkpX5/resolver-IramXe/apt_archive/./Packages - open (13: Permission denied) Get:4 file:/build/*.dsc-3nkpX5/resolver-IramXe/apt_archive ./ Packages [1405 B] Get:5 http://deb.debian.org/debian unstable InRelease [165 kB] Get:6 http://deb.debian.org/debian experimental InRelease [75.4 kB] Get:7 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB] Get:8 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB] Get:9 http://deb.debian.org/debian experimental/main Sources.diff/Index [63.3 kB] Get:10 http://deb.debian.org/debian experimental/main amd64 Packages.diff/Index [63.3 kB] Get:11 http://deb.debian.org/debian unstable/main Sources T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [62.1 kB] Get:12 http://deb.debian.org/debian unstable/main amd64 Packages T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [79.0 kB] Get:13 http://deb.debian.org/debian experimental/main Sources T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [6616 B] Get:11 http://deb.debian.org/debian unstable/main Sources T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [62.1 kB] Get:14 http://deb.debian.org/debian experimental/main amd64 Packages T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [12.1 kB] Get:12 http://deb.debian.org/debian unstable/main amd64 Packages T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [79.0 kB] Get:13 http://deb.debian.org/debian experimental/main Sources T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [6616 B] Get:14 http://deb.debian.org/debian experimental/main amd64 Packages T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [12.1 kB] Fetched 654 kB in 25s (26.1 kB/s) Reading package lists... W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list.d/sbuild-extra-repositories.list:1 W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list.d/sbuild-extra-repositories.list:1 W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list.d/sbuild-extra-repositories.list:1 W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list.d/sbuild-extra-repositories.list:1 Reading package lists... Building dependency tree... Readi
[Pkg-javascript-devel] Bug#1003940: node-esprima: FTBFS with webpack 5: Could not find *.dsc
Source: node-esprima Version: 4.0.1+ds+~4.0.3-2 Severity: important Tags: ftbfs User: pkg-javascript-devel@alioth-lists.debian.net Usertags: webpack5 Hi, We are starting to build against webpack5 in experimental and the package needed for local build is webpack and node-webpack-source from experimental. During a test rebuild, node-esprima was found to fail to build in that situation. Relevant part (hopefully): tsc -p src webpack assets by status 0 bytes [cached] 1 asset WARNING in configuration The 'mode' option has not been set, webpack will fallback to 'production' for this value. Set 'mode' option to 'development' or 'production' to enable defaults for each environment. You can also set it to 'none' to disable any default behavior. Learn more: https://webpack.js.org/configuration/mode/ ERROR in main Module not found: Error: Recursion in resolving Stack: undefined: (/<>) /<>/src/esprima.js webpack 5.65.0 compiled with 1 error and 1 warning in 364 ms make[1]: *** [debian/rules:8: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 2022-01-18T11:28:03Z Finished The full log is attached to this mail. sbuild (Debian sbuild) 0.81.2 (31 January 2021) on debian +==+ | node-esprima 4.0.1+ds+~4.0.3-2 (amd64) Tue, 18 Jan 2022 11:26:25 + | +==+ Package: node-esprima Version: 4.0.1+ds+~4.0.3-2 Source Version: 4.0.1+ds+~4.0.3-2 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: binary I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-63e24655-22d7-44b3-9d92-e379964e6008' with '<>' W: ../webpack_5.65.0+dfsg+~cs9.20.9-3_all.deb is neither a regular file nor a directory. Skipping... I: NOTICE: Log filtering will replace 'build/node-esprima-u5YFeR/resolver-C187XS' with '<>' +--+ | Update chroot| +--+ Get:1 file:/build/node-esprima-u5YFeR/resolver-QEoyxE/apt_archive ./ InRelease Ign:1 file:/build/node-esprima-u5YFeR/resolver-QEoyxE/apt_archive ./ InRelease Get:2 file:/build/node-esprima-u5YFeR/resolver-QEoyxE/apt_archive ./ Release [951 B] Get:2 file:/build/node-esprima-u5YFeR/resolver-QEoyxE/apt_archive ./ Release [951 B] Get:3 file:/build/node-esprima-u5YFeR/resolver-QEoyxE/apt_archive ./ Release.gpg Ign:3 file:/build/node-esprima-u5YFeR/resolver-QEoyxE/apt_archive ./ Release.gpg Get:4 file:/build/node-esprima-u5YFeR/resolver-QEoyxE/apt_archive ./ Packages [807 B] Err:4 file:/build/node-esprima-u5YFeR/resolver-QEoyxE/apt_archive ./ Packages Could not open file /build/node-esprima-u5YFeR/resolver-QEoyxE/apt_archive/./Packages - open (13: Permission denied) Get:4 file:/build/node-esprima-u5YFeR/resolver-QEoyxE/apt_archive ./ Packages [1405 B] Get:5 http://deb.debian.org/debian unstable InRelease [165 kB] Get:6 http://deb.debian.org/debian experimental InRelease [75.4 kB] Get:7 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB] Get:8 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB] Get:9 http://deb.debian.org/debian experimental/main Sources.diff/Index [63.3 kB] Get:10 http://deb.debian.org/debian experimental/main amd64 Packages.diff/Index [63.3 kB] Get:11 http://deb.debian.org/debian unstable/main Sources T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [62.1 kB] Get:12 http://deb.debian.org/debian unstable/main amd64 Packages T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [79.0 kB] Get:13 http://deb.debian.org/debian experimental/main Sources T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [6616 B] Get:11 http://deb.debian.org/debian unstable/main Sources T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [62.1 kB] Get:14 http://deb.debian.org/debian experimental/main amd64 Packages T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [12.1 kB] Get:12 http://deb.debian.org/debian unstable/main amd64 Packages T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [79.0 kB] Get:13 http://deb.debian.org/debian experimental/main Sources T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [6616 B] Get:14 http://deb.debian.org/debian experimental/main amd64 Packages T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [12.1 kB] Fetched 654 kB in 9s (76.8 kB/s) Reading package lists... W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list.d/sbuild-extra-repositories.list:1 W: Target Packages
[Pkg-javascript-devel] Bug#1003937: node-merge: FTBFS with webpack 5: Module not found: Error: Recursion in resolving
Source: node-merge Version: 2.1.1+ds-2 Severity: important Tags: ftbfs User: pkg-javascript-devel@alioth-lists.debian.net Usertags: webpack5 Hi, We are starting to build against webpack5 in experimental and the package needed for local build is webpack and node-webpack-source from experimental. During a test rebuild, node-merge was found to fail to build in that situation. Relevant part (hopefully): tsc -p tsconfig.json webpack --config webpack.config.js assets by status 0 bytes [cached] 1 asset ERROR in main Module not found: Error: Recursion in resolving Stack: undefined: (/<>) /<>/lib/src/index.js webpack 5.65.0 compiled with 1 error in 350 ms assets by status 99 bytes [cached] 1 asset ERROR in main Module not found: Error: Recursion in resolving Stack: undefined: (/<>) /<>/lib/src/index.js webpack 5.65.0 compiled with 1 error in 290 ms assets by status 99 bytes [cached] 1 asset ERROR in main Module not found: Error: Recursion in resolving Stack: undefined: (/<>) /<>/lib/test/index.js webpack 5.65.0 compiled with 1 error in 285 ms make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:12: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 2022-01-18T11:35:30Z Finished The full log is attached to this mail. sbuild (Debian sbuild) 0.81.2 (31 January 2021) on debian +==+ | node-merge 2.1.1+ds-2 (amd64)Tue, 18 Jan 2022 11:34:13 + | +==+ Package: node-merge Version: 2.1.1+ds-2 Source Version: 2.1.1+ds-2 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: binary I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-23256653-2233-4ae5-9eb0-11773b31523b' with '<>' W: ../webpack_5.65.0+dfsg+~cs9.20.9-3_all.deb is neither a regular file nor a directory. Skipping... I: NOTICE: Log filtering will replace 'build/node-merge-sgE4nr/resolver-1TSQHn' with '<>' +--+ | Update chroot| +--+ Get:1 file:/build/node-merge-sgE4nr/resolver-MBbAxT/apt_archive ./ InRelease Ign:1 file:/build/node-merge-sgE4nr/resolver-MBbAxT/apt_archive ./ InRelease Get:2 file:/build/node-merge-sgE4nr/resolver-MBbAxT/apt_archive ./ Release [951 B] Get:2 file:/build/node-merge-sgE4nr/resolver-MBbAxT/apt_archive ./ Release [951 B] Get:3 file:/build/node-merge-sgE4nr/resolver-MBbAxT/apt_archive ./ Release.gpg Ign:3 file:/build/node-merge-sgE4nr/resolver-MBbAxT/apt_archive ./ Release.gpg Get:4 file:/build/node-merge-sgE4nr/resolver-MBbAxT/apt_archive ./ Packages [807 B] Err:4 file:/build/node-merge-sgE4nr/resolver-MBbAxT/apt_archive ./ Packages Could not open file /build/node-merge-sgE4nr/resolver-MBbAxT/apt_archive/./Packages - open (13: Permission denied) Get:4 file:/build/node-merge-sgE4nr/resolver-MBbAxT/apt_archive ./ Packages [1405 B] Get:5 http://deb.debian.org/debian unstable InRelease [165 kB] Get:6 http://deb.debian.org/debian experimental InRelease [75.4 kB] Get:7 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB] Get:8 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB] Get:9 http://deb.debian.org/debian experimental/main Sources.diff/Index [63.3 kB] Get:10 http://deb.debian.org/debian experimental/main amd64 Packages.diff/Index [63.3 kB] Get:11 http://deb.debian.org/debian unstable/main Sources T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [62.1 kB] Get:12 http://deb.debian.org/debian unstable/main amd64 Packages T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [79.0 kB] Get:13 http://deb.debian.org/debian experimental/main Sources T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [6616 B] Get:11 http://deb.debian.org/debian unstable/main Sources T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [62.1 kB] Get:14 http://deb.debian.org/debian experimental/main amd64 Packages T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [12.1 kB] Get:12 http://deb.debian.org/debian unstable/main amd64 Packages T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [79.0 kB] Get:13 http://deb.debian.org/debian experimental/main Sources T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [6616 B] Get:14 http://deb.debian.org/debian experimental/main amd64 Packages T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [12.1 kB] Fetched 654 kB in 9s (76.4 kB/s) Reading package lists... W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list
[Pkg-javascript-devel] Bug#1003938: node-js-beautify: FTBFS with webpack 5: Module not found: Error: Recursion in resolving
Source: node-js-beautify Version: 1.14.0+dfsg+~0.15.3-1 Severity: important Tags: ftbfs User: pkg-javascript-devel@alioth-lists.debian.net Usertags: webpack5 Hi, We are starting to build against webpack5 in experimental and the package needed for local build is webpack and node-webpack-source from experimental. During a test rebuild, node-js-beautify was found to fail to build in that situation. Relevant part (hopefully): ERROR in main Module not found: Error: Recursion in resolving Stack: undefined: (/<>) ./js/src/index.js webpack 5.65.0 compiled with 1 error in 521 ms assets by status 0 bytes [cached] 1 asset ERROR in main Module not found: Error: Recursion in resolving Stack: undefined: (/<>) ./js/src/index.js webpack 5.65.0 compiled with 1 error in 340 ms asset legacy_beautify_css.js 104 bytes [emitted] (name: beautify_css) asset legacy_beautify_html.js 104 bytes [emitted] (name: beautify_html) asset legacy_beautify_js.js 104 bytes [emitted] (name: beautify_js) ERROR in beautify_css Module not found: Error: Recursion in resolving Stack: undefined: (/<>) ./js/src/css/index.js ERROR in beautify_html Module not found: Error: Recursion in resolving Stack: undefined: (/<>) ./js/src/html/index.js ERROR in beautify_js Module not found: Error: Recursion in resolving Stack: undefined: (/<>) ./js/src/javascript/index.js webpack 5.65.0 compiled with 3 errors in 408 ms dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exit code 1 make: *** [debian/rules:10: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 2022-01-18T11:34:05Z Finished The full log is attached to this mail. sbuild (Debian sbuild) 0.81.2 (31 January 2021) on debian ++ | node-js-beautify 1.14.0+dfsg+~0.15.3-1 (amd64) Tue, 18 Jan 2022 11:32:54 + | ++ Package: node-js-beautify Version: 1.14.0+dfsg+~0.15.3-1 Source Version: 1.14.0+dfsg+~0.15.3-1 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: binary I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-5b40eb08-461a-4b62-84e2-492d699f5c0a' with '<>' W: ../webpack_5.65.0+dfsg+~cs9.20.9-3_all.deb is neither a regular file nor a directory. Skipping... I: NOTICE: Log filtering will replace 'build/node-js-beautify-CQc5AL/resolver-y4WTR4' with '<>' +--+ | Update chroot| +--+ Get:1 file:/build/node-js-beautify-CQc5AL/resolver-R8jLXz/apt_archive ./ InRelease Ign:1 file:/build/node-js-beautify-CQc5AL/resolver-R8jLXz/apt_archive ./ InRelease Get:2 file:/build/node-js-beautify-CQc5AL/resolver-R8jLXz/apt_archive ./ Release [951 B] Get:2 file:/build/node-js-beautify-CQc5AL/resolver-R8jLXz/apt_archive ./ Release [951 B] Get:3 file:/build/node-js-beautify-CQc5AL/resolver-R8jLXz/apt_archive ./ Release.gpg Ign:3 file:/build/node-js-beautify-CQc5AL/resolver-R8jLXz/apt_archive ./ Release.gpg Get:4 file:/build/node-js-beautify-CQc5AL/resolver-R8jLXz/apt_archive ./ Packages [807 B] Err:4 file:/build/node-js-beautify-CQc5AL/resolver-R8jLXz/apt_archive ./ Packages Could not open file /build/node-js-beautify-CQc5AL/resolver-R8jLXz/apt_archive/./Packages - open (13: Permission denied) Get:4 file:/build/node-js-beautify-CQc5AL/resolver-R8jLXz/apt_archive ./ Packages [1405 B] Get:5 http://deb.debian.org/debian unstable InRelease [165 kB] Get:6 http://deb.debian.org/debian experimental InRelease [75.4 kB] Get:7 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB] Get:8 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB] Get:9 http://deb.debian.org/debian experimental/main Sources.diff/Index [63.3 kB] Get:10 http://deb.debian.org/debian experimental/main amd64 Packages.diff/Index [63.3 kB] Get:11 http://deb.debian.org/debian unstable/main Sources T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [62.1 kB] Get:12 http://deb.debian.org/debian unstable/main amd64 Packages T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [79.0 kB] Get:13 http://deb.debian.org/debian experimental/main Sources T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [6616 B] Get:11 http://deb.debian.org/debian unstable/main Sources T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [62.1 kB] Get:14 http://deb.debian.org/debian experimental/main amd64 Packages T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [12.1 kB] Get:12 http://deb.debian.org/debian unstable/main amd64 Packages T-2022-01-18-0802.10-F-2022-01-17-0803.35.pdiff [79.0 kB] Get:13
[Pkg-javascript-devel] RFS: lumino
Hi there, I just updated the lumino package from 2021.12.13-1 to 2021.12.13-2. Which fixes one of the bugs encountered when reverse building with webpack 5. Here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003884. I would like you to confirm if it's safe for sponsorship and uploading https://salsa.debian.org/calebpitan/lumino Thank you! Caleb Adepitan OpenPGP_0x8A1B2CC96775D2D7.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1003884: lumino: FTBFS with webpack 5: Not found, setimmediate is required by debian/nodejs/./extlinks but not available
Source: lumino Version: 2021.12.13-1 Severity: important Tags: ftbfs User: pkg-javascript-devel@alioth-lists.debian.net Usertags: webpack5 Hi, We are starting to build against webpack5 in experimental and the package needed for local build is webpack and node-webpack-source from experimental. During a test rebuild, lumino was found to fail to build in that situation. Relevant part (hopefully): Found debian/nodejs/additional_components Adding component(s): packages/algorithm, packages/application, packages/collections, packages/commands, packages/coreutils, packages/datagrid, packages/datastore, packages/default-theme, packages/disposable, packages/domutils, packages/dragdrop, packages/keyboard, packages/messaging, packages/polling, packages/properties, packages/signaling, packages/virtualdom, packages/widgets Not found ### setimmediate is required by debian/nodejs/./extlinks but not available make: *** [debian/rules:4: binary] Error 1 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 2022-01-17T10:12:52Z Finished The full log is attached to this mail. sbuild (Debian sbuild) 0.81.2 (31 January 2021) on debian +==+ | lumino 2021.12.13-1 (amd64) Mon, 17 Jan 2022 14:29:10 + | +==+ Package: lumino Version: 2021.12.13-1 Source Version: 2021.12.13-1 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: binary I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-103a53e2-d3f1-4b81-b08c-150e2e7aecfe' with '<>' W: ../webpack_5.65.0+dfsg+~cs9.20.9-3_all.deb is neither a regular file nor a directory. Skipping... I: NOTICE: Log filtering will replace 'build/lumino-cRAxzs/resolver-Rk4U25' with '<>' +--+ | Update chroot| +--+ Get:1 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ InRelease Ign:1 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ InRelease Get:2 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ Release [951 B] Get:2 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ Release [951 B] Get:3 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ Release.gpg Ign:3 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ Release.gpg Get:4 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ Packages [807 B] Err:4 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ Packages Could not open file /build/lumino-cRAxzs/resolver-OA3Elp/apt_archive/./Packages - open (13: Permission denied) Get:4 file:/build/lumino-cRAxzs/resolver-OA3Elp/apt_archive ./ Packages [1405 B] Get:5 http://deb.debian.org/debian unstable InRelease [165 kB] Get:6 http://deb.debian.org/debian experimental InRelease [75.4 kB] Get:7 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB] Get:8 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB] Get:9 http://deb.debian.org/debian unstable/main Sources T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [6783 B] Get:10 http://deb.debian.org/debian experimental/main Sources.diff/Index [63.3 kB] Get:9 http://deb.debian.org/debian unstable/main Sources T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [6783 B] Get:11 http://deb.debian.org/debian experimental/main amd64 Packages.diff/Index [63.3 kB] Get:12 http://deb.debian.org/debian unstable/main amd64 Packages T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [6743 B] Get:13 http://deb.debian.org/debian experimental/main Sources T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [1644 B] Get:14 http://deb.debian.org/debian experimental/main amd64 Packages T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [900 B] Get:12 http://deb.debian.org/debian unstable/main amd64 Packages T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [6743 B] Get:14 http://deb.debian.org/debian experimental/main amd64 Packages T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [900 B] Get:13 http://deb.debian.org/debian experimental/main Sources T-2022-01-17-0803.35-F-2022-01-17-0803.35.pdiff [1644 B] Fetched 510 kB in 6s (85.3 kB/s) Reading package lists... W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list.d/sbuild-extra-repositories.list:1 W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:4 and /etc/apt/sources.list.d/sbuild-extra-repositories.list:1 W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:4
[Pkg-javascript-devel] Bug#1003502: node-jsonld: FTBFS with webpack 5: Invalid configuration object
Source: node-jsonld
Version: 4.0.1-1
Severity: important
Tags: ftbfs
User: pkg-javascript-devel@alioth-lists.debian.net
Usertags: webpack5
Hi,
We are starting to build against webpack5 in experimental and the
package needed for local build is webpack and node-webpack-source from
experimental.
During a test rebuild, node-jsonld was found to fail to build in that
situation.
Relevant part (hopefully):
Successfully compiled 23 files with Babel (5258ms).
webpack --progress
[webpack-cli] Invalid configuration object. Webpack has been initialized
using a configuration object that does not match the API schema.
- configuration[0].module.rules[0] should be one of these:
["..." | object { assert?, compiler?, dependency?, descriptionData?,
enforce?, exclude?, generator?, include?, issuer?, issuerLayer?, layer?,
loader?, mimetype?, oneOf?, options?, parser?, realResource?, resolve?,
resource?, resourceFragment?, resourceQuery?, rules?, scheme?,
sideEffects?, test?, type?, use? }, ...]
-> A rule.
Details:
* configuration[0].module.rules[0].include[0] has an unknown
property 'exclude'. These properties are valid:
object { and?, not?, or? }
-> Logic operators used in a condition matcher.
* configuration[0].module.rules[0].include[1] has an unknown
property 'include'. These properties are valid:
object { and?, not?, or? }
-> Logic operators used in a condition matcher.
* configuration[0].module.rules[0].include[0] has an unknown
property 'exclude'. These properties are valid:
object { and?, not?, or? }
-> Logic operators used in a condition matcher.
* configuration[0].module.rules[0].include[1] has an unknown
property 'include'. These properties are valid:
object { and?, not?, or? }
-> Logic operators used in a condition matcher.
- configuration[0].node should be one of these:
false | object { __dirname?, __filename?, global? }
-> Include polyfills or mocks for various node stuff.
Details:
* configuration[0].node has an unknown property 'Buffer'. These
properties are valid:
object { __dirname?, __filename?, global? }
-> Options object for node compatibility features.
* configuration[0].node has an unknown property 'crypto'. These
properties are valid:
object { __dirname?, __filename?, global? }
-> Options object for node compatibility features.
* configuration[0].node has an unknown property 'process'. These
properties are valid:
object { __dirname?, __filename?, global? }
-> Options object for node compatibility features.
* configuration[0].node has an unknown property 'setImmediate'.
These properties are valid:
object { __dirname?, __filename?, global? }
-> Options object for node compatibility features.
- configuration[1].module.rules[0] should be one of these:
["..." | object { assert?, compiler?, dependency?, descriptionData?,
enforce?, exclude?, generator?, include?, issuer?, issuerLayer?, layer?,
loader?, mimetype?, oneOf?, options?, parser?, realResource?, resolve?,
resource?, resourceFragment?, resourceQuery?, rules?, scheme?,
sideEffects?, test?, type?, use? }, ...]
-> A rule.
Details:
* configuration[1].module.rules[0].include[0] has an unknown
property 'exclude'. These properties are valid:
object { and?, not?, or? }
-> Logic operators used in a condition matcher.
* configuration[1].module.rules[0].include[1] has an unknown
property 'include'. These properties are valid:
object { and?, not?, or? }
-> Logic operators used in a condition matcher.
* configuration[1].module.rules[0].include[0] has an unknown
property 'exclude'. These properties are valid:
object { and?, not?, or? }
-> Logic operators used in a condition matcher.
* configuration[1].module.rules[0].include[1] has an unknown
property 'include'. These properties are valid:
object { and?, not?, or? }
-> Logic operators used in a condition matcher.
- configuration[1].node should be one of these:
false | object { __dirname?, __filename?, global? }
-> Include polyfills or mocks for various node stuff.
Details:
* configuration[1].node has an unknown property 'Buffer'. These
properties are valid:
object { __dirname?, __filename?, global? }
-> Options object for node compatibility features.
* configuration[1].node has an unknown property 'crypto'. These
properties are valid:
object { __dirname?, __filename?, global? }
-> Options object for node compatibility features.
* configuration[1].node has an unknown property 'process'. These
properties are valid:
object { __dirname?, __filename?, global? }
-> Options object for node compatibility features.
* configuration[1].node has an unknown property 'setImmediate'.
These properties are valid:
object { __dirname?, __filename?, global? }
-> Options object for node compatib
[Pkg-javascript-devel] Bug#1001683: node-babel-loader: FTBFS with webpack5: BREAKING CHANGE: No more changes should happen to Compilation.assets after sealing the Compilation
Source: node-babel-loader Version: 8.2.3-1 Severity: important Justification: ftbfs Tags: ftbfs User: pkg-javascript-devel@alioth-lists.debian.net Usertags: webpack5 Hi, We are starting to build against webpack5 in experimental and the package needed for local build is webpack and node-webpack-source from experimental. During a test rebuild, node-babel-loader was found to fail to build in that situation. Relevant part (hopefully): # should throw error (node:207301) [DEP_WEBPACK_COMPILATION_NORMAL_MODULE_LOADER_HOOK] DeprecationWarning: Compilation.hooks.normalModuleLoader was moved to NormalModule.getCompilationHooks(compilation).loader (node:207301) [DEP_WEBPACK_COMPILATION_ASSETS] DeprecationWarning: Compilation.assets will be frozen in future, all modifications are deprecated. BREAKING CHANGE: No more changes should happen to Compilation.assets after sealing the Compilation. Do changes to assets earlier, e. g. in Compilation.hooks.processAssets. Make sure to select an appropriate stage from Compilation.PROCESS_ASSETS_STAGE_*. not ok 75 should be strictly equal --- operator: equal expected: |- 'webpack://babel-loader/./test/fixtures/basic.js' actual: |- 'webpack://babel-loader/webpack/bootstrap' at: (/<>/test/sourcemaps.test.js:123:15) stack: |- Error: should be strictly equal at Test.assert [as _assert] (/usr/share/nodejs/tape/lib/test.js:311:54) at Test.bound [as _assert] (/usr/share/nodejs/tape/lib/test.js:96:32) at Test.strictEqual (/usr/share/nodejs/tape/lib/test.js:475:10) at Test.bound [as is] (/usr/share/nodejs/tape/lib/test.js:96:32) at /<>/test/sourcemaps.test.js:123:15 at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3) ... not ok 90 should be strictly equal --- operator: equal expected: |- 'webpack://babel-loader/./test/fixtures/basic.js' actual: |- 'webpack://babel-loader/webpack/bootstrap' at: (/<>/test/sourcemaps.test.js:240:15) stack: |- Error: should be strictly equal at Test.assert [as _assert] (/usr/share/nodejs/tape/lib/test.js:311:54) at Test.bound [as _assert] (/usr/share/nodejs/tape/lib/test.js:96:32) at Test.strictEqual (/usr/share/nodejs/tape/lib/test.js:475:10) at Test.bound [as is] (/usr/share/nodejs/tape/lib/test.js:96:32) at /<>/test/sourcemaps.test.js:240:15 at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3) ... not ok 91 should be truthy --- operator: ok expected: true actual: false at: (/<>/test/sourcemaps.test.js:247:15) stack: |- Error: should be truthy at Test.assert [as _assert] (/usr/share/nodejs/tape/lib/test.js:311:54) at Test.bound [as _assert] (/usr/share/nodejs/tape/lib/test.js:96:32) at Test.assert (/usr/share/nodejs/tape/lib/test.js:430:10) at Test.bound [as ok] (/usr/share/nodejs/tape/lib/test.js:96:32) at /<>/test/sourcemaps.test.js:247:15 at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3) ... not ok 98 should be strictly equal --- operator: equal expected: |- 'webpack://babel-loader/./test/fixtures/basic.js' actual: |- 'webpack://babel-loader/webpack/bootstrap' at: (/<>/test/sourcemaps.test.js:304:15) stack: |- Error: should be strictly equal at Test.assert [as _assert] (/usr/share/nodejs/tape/lib/test.js:311:54) at Test.bound [as _assert] (/usr/share/nodejs/tape/lib/test.js:96:32) at Test.strictEqual (/usr/share/nodejs/tape/lib/test.js:475:10) at Test.bound [as is] (/usr/share/nodejs/tape/lib/test.js:96:32) at /<>/test/sourcemaps.test.js:304:15 at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3) ... not ok 99 should be truthy --- operator: ok expected: true actual: false at: (/<>/test/sourcemaps.test.js:311:15) stack: |- Error: should be truthy at Test.assert [as _assert] (/usr/share/nodejs/tape/lib/test.js:311:54) at Test.bound [as _assert] (/usr/share/nodejs/tape/lib/test.js:96:32) at Test.assert (/usr/share/nodejs/tape/lib/test.js:430:10) at Test.bound [as ok] (/usr/share/nodejs/tape/lib/test.js:96:32) at /<>/test/sourcemaps.test.js:311:15 at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3) ... The full log is attached to this mail. sbuild (Debian sbuild) 0.81.2 (31 January 2021) on debian +==+ | node-babel-loader 8.2.3-1 (amd64)Mon, 13 Dec 2021 15:06:04 + | +=
