Not sure why. But keep in mind that, the way error works sometimes is by chaining and also catching. Just because it said so doesn’t mean there is any error here. It could be another issue. Sometimes, it could be a different irrelevant issue.
With that being said, sometimes when npm installing sometimes, it doesn’t save in package.json… Have you tried to check if it is installed correctly? Does the app run normally without fawn?? How about the spelling of coma in the require(‘fawn’)? Can you show the whole error stack?
In case anyone still has this issue, just rewrite “Fawn.init(mongoose)” as “Fawn.init(‘mongodb://localhost/foo’)” in your code, if you’re using the latest version of Fawn.