iblog clone到本地后,执行npm install 然后运行 npm run dev ,出现如下错误
iblog@0.0.1 dev /home/iblog
gulp watch --mod=iblog
fs.js:27
const { Math, Object } = primordials;
^
ReferenceError: primordials is not defined
at fs.js:27:26
at req_ (/home/iblog/node_modules/_natives@1.1.6@natives/index.js:143:24)
at Object.req [as require] (/home/iblog/node_modules/_natives@1.1.6@natives/index.js:55:10)
at Object. (/home/iblog/node_modules/_graceful-fs@3.0.12@graceful-fs/fs.js:1:37)
at Module._compile (internal/modules/cjs/loader.js:958:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:994:10)
at Module.load (internal/modules/cjs/loader.js:813:32)
at Function.Module._load (internal/modules/cjs/loader.js:725:14)
at Module.require (internal/modules/cjs/loader.js:850:19)
at require (internal/modules/cjs/helpers.js:74:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! iblog@0.0.1 dev: gulp watch --mod=iblog
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the iblog@0.0.1 dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
iblog clone到本地后,执行npm install 然后运行 npm run dev ,出现如下错误
fs.js:27 const { Math, Object } = primordials; ^
ReferenceError: primordials is not defined at fs.js:27:26 at req_ (/home/iblog/node_modules/_natives@1.1.6@natives/index.js:143:24) at Object.req [as require] (/home/iblog/node_modules/_natives@1.1.6@natives/index.js:55:10) at Object. (/home/iblog/node_modules/_graceful-fs@3.0.12@graceful-fs/fs.js:1:37)
at Module._compile (internal/modules/cjs/loader.js:958:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:994:10)
at Module.load (internal/modules/cjs/loader.js:813:32)
at Function.Module._load (internal/modules/cjs/loader.js:725:14)
at Module.require (internal/modules/cjs/loader.js:850:19)
at require (internal/modules/cjs/helpers.js:74:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! iblog@0.0.1 dev:
gulp watch --mod=iblog
npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the iblog@0.0.1 dev script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.