Standard: The latest release of is-my-json-valid breaks standard

Created on 18 Dec 2017  路  3Comments  路  Source: standard/standard

Since is-my-json-valid released version 2.17.0, I get the following error when running standard:

/home/helge/.node_modules/lib/node_modules/standard/node_modules/is-my-json-valid/index.js:366
      visit(name+'['+i+']', node.items, reporter, filter, schemaPath.concat('items'))
                                                                     ^

TypeError: Cannot read property 'concat' of undefined
    at visit (/home/helge/.node_modules/lib/node_modules/standard/node_modules/is-my-json-valid/index.js:366:70)
    at /home/helge/.node_modules/lib/node_modules/standard/node_modules/is-my-json-valid/index.js:416:9
    at Array.forEach (<anonymous>)
    at visit (/home/helge/.node_modules/lib/node_modules/standard/node_modules/is-my-json-valid/index.js:409:18)
    at /home/helge/.node_modules/lib/node_modules/standard/node_modules/is-my-json-valid/index.js:543:9
    at Array.forEach (<anonymous>)
    at visit (/home/helge/.node_modules/lib/node_modules/standard/node_modules/is-my-json-valid/index.js:540:31)
    at compile (/home/helge/.node_modules/lib/node_modules/standard/node_modules/is-my-json-valid/index.js:565:3)
    at visit (/home/helge/.node_modules/lib/node_modules/standard/node_modules/is-my-json-valid/index.js:340:16)
    at /home/helge/.node_modules/lib/node_modules/standard/node_modules/is-my-json-valid/index.js:416:9

Most helpful comment

This was me 馃檲 sorry about that!

It has been fixed upstream now, and the broken version have been deprecated on npm.

Just reinstalling or manually upgrading is-my-json-valid to 2.17.1 (npm install [email protected]) should fix it 馃憣

All 3 comments

same behavior on my projects.

Looks like last is-my-json-valid version introduces a bug and is broken standard.

This was me 馃檲 sorry about that!

It has been fixed upstream now, and the broken version have been deprecated on npm.

Just reinstalling or manually upgrading is-my-json-valid to 2.17.1 (npm install [email protected]) should fix it 馃憣

Thanks @LinusU! 馃憤

Was this page helpful?
0 / 5 - 0 ratings

Related issues

johannes-z picture johannes-z  路  3Comments

muhajirdev picture muhajirdev  路  3Comments

ghost picture ghost  路  3Comments

Alexsey picture Alexsey  路  3Comments

Jakobud picture Jakobud  路  3Comments