Closed michaelwittig closed 9 years ago
Did you ever figure out the underlying cause?
Hi Mark,
As far as I remember the problem was solved by a newer version of node-toobusy.
Are you using the latest version? which version of node are you running?
Michael
Am 08.07.2014 um 22:13 schrieb Mark Stosberg notifications@github.com:
Did you ever figure out the underlying cause?
— Reply to this email directly or view it on GitHub.
Thanks for the reply.
I was actually getting Error: Cannot find module 'mime' on install ' on a different project, and was trying to understand why. From searching that phrase, a fair number of people have run into it, and often don't understand why.... likely because the core issue has nothing to do with not finding the
mime` module. In my case, I think I might have been run into
into some kind of a stale module cache issue.
On Thu, Jul 10, 2014 at 12:57 AM, Michael Wittig notifications@github.com wrote:
Hi Mark,
As far as I remember the problem was solved by a newer version of node-toobusy.
Are you using the latest version? which version of node are you running?
Michael
Am 08.07.2014 um 22:13 schrieb Mark Stosberg notifications@github.com:
Did you ever figure out the underlying cause?
Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub https://github.com/lloyd/node-toobusy/issues/19#issuecomment-48565287.
Mark Stosberg
Senior Systems Engineer
RideAmigos
When I try to npm install toobusy I get the following error with node > 0.10.10. It works with 0.10.10.