New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
window安装问题 #3344
Comments
还是安装问题,git,node都有了 |
Can you post your environment details , eg node version ? |
@vae-Eason 建议换npm试试,cnpm有时候会有些莫名其妙的坑。前面好像有issues提到是权限问题,可以参考下 |
我换了两个版本一个是10开头,一个8开头,都不行哈 |
So,how to solve the problem finally. I have the same problem in mac environment. node version is v11.2.0 |
See mozilla/nunjucks#1169 might be linked |
i have solve the problem. in mac you cant install nodejs by brew , it will give you the latest version of nodejs ,not the LTS version . you must download the package from https://nodejs.org!. get the LTS version! |
This issue has been automatically marked as stale because lack of recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
$ cnpm install -g hexo
npm WARN deprecated titlecase@1.1.2: no longer maintained
npm WARN deprecated postinstall-build@5.0.3: postinstall-build's behavior is now built into npm! You should migrate off of postinstall-build and use the new
prepare
lifecycle script with npm 5.0.0 or greater.C:\Users\Administrator\AppData\Roaming\npm\hexo -> C:\Users\Administrator\AppData\Roaming\npm\node_modules\hexo\bin\hexo
'node' ▒▒▒▒▒ڲ▒▒▒▒ⲿ▒▒▒Ҳ▒▒▒ǿ▒▒▒▒еij▒▒▒
▒▒▒▒▒▒▒▒▒ļ▒▒▒
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules\hexo\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! nunjucks@3.1.3 postinstall:
node postinstall-build.js src
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the nunjucks@3.1.3 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Administrator.npm.cache\cnpm_logs\2018-11-08T09_09_53_790Z-debug.log
The text was updated successfully, but these errors were encountered: