-
Notifications
You must be signed in to change notification settings - Fork 23
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
TypeError: Cannot read property 'single' of undefined #11
Comments
能把node版本发一下吗? |
node 8.9.4
| |
杨森
邮箱:13554342109@163.com
|
签名由 网易邮箱大师 定制
在2018年02月09日 21:40,Alchemy 写道:
能把node版本发一下吗?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
我也是报相同的错误,显示TypeError: Cannot read property 'single' of undefined |
Duplicate of #12 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
E:\workNode\Blog\Spruche\routes\admin.js:23
const friendImgUpload = upload.friendImgUpload.single('friendhead');
^
TypeError: Cannot read property 'single' of undefined
at Object. (E:\workNode\Blog\Spruche\routes\admin.js:23:48)
at Module._compile (module.js:643:30)
at Object.Module._extensions..js (module.js:654:10)
at Module.load (module.js:556:32)
at tryModuleLoad (module.js:499:12)
at Function.Module._load (module.js:491:3)
at Module.require (module.js:587:17)
at require (internal/module.js:11:18)
at Object. (E:\workNode\Blog\Spruche\app.js:17:15)
at Module._compile (module.js:643:30)
at Object.Module._extensions..js (module.js:654:10)
at Module.load (module.js:556:32)
at tryModuleLoad (module.js:499:12)
at Function.Module._load (module.js:491:3)
at Module.require (module.js:587:17)
at require (internal/module.js:11:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! spruche@0.1.1 start:
node --harmony ./bin/www
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the spruche@0.1.1 start 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\JasonYang\AppData\Roaming\npm-cache_logs\2018-02-09T09_08_03_940Z-debug.log
The text was updated successfully, but these errors were encountered: