Repository navigation
"utils.files is not a function" (mocha: 5.0.2) #3265
Description
Description
Hey, i've just upgraded to the latest mocha version 5.0.2 and I now start to see a "utils.files is not a function" error when running in watch mode with passing a glob path. Seems this commit ec8901a removed the function which is still used in https://github.com/mochajs/mocha/blob/master/bin/_mocha#L532
Steps to Reproduce
NODE_ENV=test mocha './test/**/*.js'
Expected behavior:
it should execute my tests as before.
Actual behavior:
it crashes all the time
> NODE_ENV=test mocha './test/**/*.js' "--watch"
/opt/MY-PACKAGE/node_modules/mocha/bin/_mocha:532
const watchFiles = utils.files(cwd, [ 'js' ].concat(program.watchExtensions));
^
TypeError: utils.files is not a function
at Object.<anonymous> (/opt/MY-PACKAGE/node_modules/mocha/bin/_mocha:532:28)
at Module._compile (module.js:643:30)
at Object.Module._extensions..js (module.js:654:10)
at Module.load (module.js:556:32)
at tryModuleLoad (module.js:499:12)
at Function.Module._load (module.js:491:3)
at Function.Module.runMain (module.js:684:10)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3Versions
5.0.2- shell: zsh
- The code transpiler being used: babel
Reacted by kenan-rhoton, Christophe Benoit, Alex Disler, Ryan, Andrew Kiellor, Dmitry Mazurok, Tim Mensch, rryanrussell, Chris Chang, Phil Gold and 3 more
Activity
[-]"utils.files is not a function"[/-][+]"utils.files is not a function" (mocha: 5.0.2)[/+]remolueoend commentedon Mar 6, 2018
Same here, looks like
utils.fileswas removed in ec8901a but is still in use at https://github.com/mochajs/mocha/blob/master/bin/_mocha#L532.archae0pteryx commentedon Mar 6, 2018
This exists in 5.0.1 as well it seems.
arichiardi commentedon Mar 7, 2018
Confirm this is still an issue.
ihsw commentedon Mar 7, 2018
Downgraded to 5.0.1, it works.
sebs commentedon May 9, 2018
Error exists in 5.11, node 9.5.0 as well
Downgrade to 5.0.0 fixed it.
sebs commentedon May 9, 2018
Please reopen.
boneskull commentedon May 9, 2018
@sebs This has already been fixed; please check that the
mochayou are executing is indeed v5.1.1; you may need to runmocha -v. sometimes a globally-installed mocha is used by mistakesebs commentedon May 10, 2018
Ah I donnu, I was so sure I had pinned it down to 5.1.1 Mocha works as intended
Thanks