Hexo: { Error: Cannot find module './build/Release/DTraceProviderBindings'
still suffered
{ Error: Cannot find module './build/Release/DTraceProviderBindings'
i've tried all the two solution above this issue
npm uninstall hexo-cli -g
npm install hexo-cli -g
and
npm install hexo --opential
but all of this two doesn't work
I used macbook air and the npm version is 4.2.0 and node version is v7.8.0
the error message i got is
{ Error: Cannot find module './build/Release/DTraceProviderBindings' at Function.Module._resolveFilename (module.js:470:15) at Function.Module._load (module.js:418:25) at Module.require (module.js:498:17) at require (internal/module.js:20:19) at Object.
Are there any other solution?
moreoronce
All 10 comments
Have you tried npm install hexo-cli --no-optional?
NoahDragon
on 11 Apr 2017
@NoahDragon i've tried this command to install hexo. But after that when i inputed the hexo command, the shell told me command can not found.
moreoronce
on 12 Apr 2017
Does the hexo init working?
What's the nodejs version and npm version?
NoahDragon
on 12 Apr 2017
@NoahDragon no， hexo init doesn't work.
my nodejs' version is V7.8.0 and the npm's version is 4.2.0
moreoronce
on 12 Apr 2017
This issue looks like related to nodejs prefix. http://stackoverflow.com/questions/15054388/global-node-modules-not-installing-correctly-command-not-found
Or the npm directory is not set in PATH variable. http://stackoverflow.com/questions/29955217/global-npm-package-installed-but-command-not-found
If the above two do not fix the issue, I probably need more info to investigate the issue, like what's your OS, have you installed other global package via npm?
NoahDragon
on 12 Apr 2017
Did some digging. This happens when the system python is 3.x.
https://github.com/trentm/node-bunyan/issues/216
I set my system python to 2.7.13, uninstalled hexo-cli and all local hexo packages, then reinstalled with npm install -g hexo-cli -O && npm install -O and dtrace built successfully.
nicholascloud
on 26 May 2017
I come across this issues several times. Could we rewrite hexo-log so that it does not use bunyan anymore? As dtrace-provider is an optional dependencies of bunyan and I guess we haven't use any related routines.
JLHwung
on 21 Jul 2017
@JLHwung You are right. If we could only opt-out the DTrace-provider in bunyan, we can solve this issue once for all. Probably create a hexo-bunyan, without the DTrace-provider as an optional.
NoahDragon
on 21 Jul 2017
In my case, npm install hexo-cli --no-optional was not working. However, npm rebuild could solve this problem.
kyasbal-1994
on 30 Aug 2017
curbengh
on 9 Dec 2019
Related issues
jakeg
·
3Comments
jo4x962k7JL
·
3Comments
ghost
·
3Comments
demurgos
·
3Comments
awulkan
·
3Comments
Most helpful comment
Did some digging. This happens when the system python is 3.x.
https://github.com/trentm/node-bunyan/issues/216
I set my system python to 2.7.13, uninstalled hexo-cli and all local hexo packages, then reinstalled with
npm install -g hexo-cli -O && npm install -Oand dtrace built successfully.