debug: exports.useColors is not a function

Everything was working fine Friday. Had to reinstall fresh all my npm packages this morning, and I got this error in my webpack-dev-server

As I didn’t change anything to my package.json (and I’m not using directly debug) I suspect an update in the last days broke things. The only package I have using the most recent debug version is babel-core@6.17.0 (-> debug@2.4.5)

My webpack@1.13.2 and webpack-dev-server@1.16.2 use debug@2.2.0

I have no idea how to solve this issue right now, so if someone has clues I’d be happy to help

Extract of debug.js causing the problem :

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 6
Comments: 16 (4 by maintainers)

Most upvoted comments

@DaveGee For posterity, I’m curious as to what your webpack.config.js file looks like.

TooTallNate on Dec 21, 2016

This is insane. Adding the lines about bower.json in the config of webpack solves the issue apparently, although I repeat : I do not use bower, and have no bower.json, nor .bower.json file anywhere in my own code

So I must add a config line about a tool I don’t use for my code to work. Anyone has an explanation about this ?

Thanks for your help

I’ll look more into this, as I won’t let my config files get messy with unrelated stuff. I think I prefer the shrinkwrap way

DaveGee on Dec 21, 2016

For now I had to npm shrinkwrap and fix the version number of debug to 2.3.0 for my build to work again. There was also superagent, eslint and other packages that were using debug > 2.2.0

DaveGee on Dec 19, 2016