Open pallas42 opened 3 years ago
Have you run npm i
in the plugin directory?
Thanks!
npm i
shows lots of packages deprecated, so I ran npm upgrade
and then npm i
, the result as follows.
While the "Current backend: node is not available!" issue persists.
➜ npm i
> nodejieba@2.4.2 install
> node-pre-gyp install --fallback-to-build
node-pre-gyp info it worked if it ends with ok
node-pre-gyp info using node-pre-gyp@0.14.0
node-pre-gyp info using node@15.0.1 | darwin | x64
node-pre-gyp WARN Using request for node-pre-gyp https download
[nodejieba] Success: "/Users/pallas/node_modules/nodejieba/build/Release/nodejieba.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile
node-pre-gyp info ok
up to date in 1s
The issue persists after upgrading nodejieba to @2.5.1. (The local nodejieba module is working properly in terminal)
这个库作者还维护吗?这么久了这个还是open
这个库作者还维护吗?这么久了这个还是open
因为俺没法复现
This should be a problem with doom emacs
. More specifically, it's a problem with straight.el
. it just add .el files to the load path.
问题可能是在use-package
的:load-path
,它不能直接传字符串,要传一个函数(我看了我的配置才发现)
:load-path (lambda () "xxxx")
doom emacs
M-x jieba-forward-word
后报错 "Current backend: node is not available!"emacs --debug-init
报错的backtrace:config.el
中的配置:nodejieba貌似是安装成功的 cli下
npm list
显示nodejieba@2.4.2