Package: node-schema-utils Version: 3.1.1~ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source Control: found -1 4.0.0~ds-1
Hi,
node-schema-utils recently started to FTBFS in sid (but not yet in
testing):
dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/schema-utils
/bin/sh -ex debian/tests/pkg-js/test
+ jest --ci test/
PASS test/range.test.js
PASS test/hints.test.js
PASS test/api.test.js
FAIL test/index.test.js (6.825 s)
● Validation › should fail validation for postFormatter #1
expect(received).toMatchSnapshot()
Snapshot name: `Validation should fail validation for postFormatter #1 1`
- Snapshot - 1
+ Received + 1
@@ -5,11 +5,11 @@
For loader options: webpack >= v2.0.0 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
+ // test: /\.xxx$/, // may apply this only for some modules
options: {
minify: …
}
})
]"
413 | minify: true,
414 | },
> 415 | (msg) => expect(msg).toMatchSnapshot(),
| ^
416 | {
417 | name: "Webpack",
418 | baseDataPath: "configuration",
at fn (test/index.test.js:415:26)
at Object.<anonymous> (test/index.test.js:45:9)
● Validation › should fail validation for postFormatter #2
expect(received).toMatchSnapshot()
Snapshot name: `Validation should fail validation for postFormatter #2 1`
- Snapshot - 1
+ Received + 1
"Invalid configuration object. Webpack has been initialized using a
configuration object that does not match the API schema.
- - configuration.output.filename: A relative path is expected. However,
the provided value \"/bar\" is an absolute path!
+ - configuration.output.filename: A relative path is expected. However,
the provided value "/bar" is an absolute path!
Please use output.path to specify absolute path and output.filename
for the file name."
453 | },
454 | },
> 455 | (msg) => expect(msg).toMatchSnapshot(),
| ^
456 | {
457 | name: "Webpack",
458 | baseDataPath: "configuration",
at fn (test/index.test.js:455:26)
at Object.<anonymous> (test/index.test.js:45:9)
● Validation › should fail validation for ! in path
expect(received).toMatchSnapshot()
Snapshot name: `Validation should fail validation for ! in path 1`
- Snapshot - 1
+ Received + 1
"Invalid configuration object. Object has been initialized using a
configuration object that does not match the API schema.
- - configuration.output.path: The provided value \"/somepath/!test\"
contains exclamation mark (!) which is not allowed because it's reserved for
loader syntax.
+ - configuration.output.path: The provided value "/somepath/!test"
contains exclamation mark (!) which is not allowed because it's reserved for
loader syntax.
-> The output directory as **absolute path** (required)."
609 | },
610 | },
> 611 | (msg) => expect(msg).toMatchSnapshot()
| ^
612 | );
613 |
614 | createFailedTestCase(
at fn (test/index.test.js:611:26)
at Object.<anonymous> (test/index.test.js:45:9)
...
Some output formatting (escaping) seems to have changed.
Andreas
node-schema-utils.sid.build.gz
Description: application/gzip
