with node-source-map 0.7 built from salsa master branch, there is only
1 failure. 26 tests were failing earlier with node-source-map 0.6.
This is a red herring.
The autopkgtest fails aren't related to node-source-map at all.
Specifically, the tests don't fail in gbp buildpackage, but
anywhere else). The job is done (see debian/rules), we just have to find
the good dependencies and fix the build since built wasm isn't exactly
what upstream embeds in node-source-map, maybe some unpublished work...
I'm not exactly sure if the build is broken. The artifact generated by
the
On Wed, 11 May 2022 11:23:52 +0200 Georges Khaznadar
wrote:
Hello,
the errors raised during the build of node-ktex are due to an error
which comes from node-postcss-loader
I can confirm the bug is in node-postcss-loader
It is because webpack 5 is required for this version of
On the other hand, the autoprefixer.js from the gem (about 1 MB) and the
autoprefixer.js that's generated through build from the upstream repo
(about 8 MB) seems to be different. This is unexplained by the dev.
I was comparing an older version of the gem actually. Please ignore this
There is a possibility that this is related to the execjs version.
https://github.com/ai/autoprefixer-rails/issues/203#issuecomment-838512342
On the other hand, the autoprefixer.js from the gem (about 1 MB) and the
autoprefixer.js that's generated through build from the upstream repo
(about
https://stackoverflow.com/questions/33505992/babel-6-changes-how-it-exports-default
But most importantly
https://kentcdodds.com/blog/misunderstanding-es6-modules-upgrading-babel-tears-and-a-solution
03-Jul-2021 16:56:56 Pirate Praveen :
> Control: reopen -1
>
> On Wed, 30 Jun 2021 22:40:13
This is most likely due to babel-plugin-add-module-exports being broken.
See https://github.com/59naga/babel-plugin-add-module-exports/issues/72
and https://github.com/59naga/babel-plugin-add-module-exports/issues/80
and https://github.com/59naga/babel-plugin-add-module-exports/issues/73
A few observations.
1) The commit
https://github.com/rollup/plugins/commit/1459cf0ab5e5eb7beee46f52bc4dbbb88d3e4335#diff-c68d63c5e10e04a850c0ea8abd479dbb77c794b3aadecf91483dcf3df96156df
which prevents exceptions from being silently ignored maybe the reason
why this is starting to err.
2)
gbp:error: upstream/1.22.10+_cs18.39.16 is not a valid treeish
indeed your fork only has 33 tags, whereas js-team/node-yarnpkg has 37.
Please pull those tags and push them to your fork, then force restart the CI
pipeline.
This would help us to see if your proposed fix works.
Pushing tags
There are some 4 pipes before the finish event. I'm looking through each
one of them to see if there's a mismatch.
It seems to be tar-fs
Please see https://salsa.debian.org/js-team/node-yarnpkg/-/merge_requests/4
I've just downloaded the latest version from the github of tar-fs and
> >I think the real issue is that it does not pull not-yet-cached
modules.
>
I did some console.log debugging yesterday.
The tarball-fetcher, for whatever be the reason, doesn't ever trigger
the .on('finish' event
> Since yarnpkg add command did not return an error, the autpkgtest was
> succeeding even though it did not add any modules to node_modules
> directory.
>
I did a bisect (sort of).
Removing cache is not an issue till commit 232ee703 (New upstream version
1.22.4+debian)
But, it is an issue
> Since yarnpkg add command did not return an error, the autpkgtest was
> succeeding even though it did not add any modules to node_modules
> directory.
>
I did a bisect (sort of).
Removing cache is not an issue till commit 232ee703 (New upstream version
1.22.4+debian)
But, it is an issue
13 matches
Mail list logo
