-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
Windows下面运行gen直接NPM报错退出 #22
Comments
Reinstall v1.4.5 |
@HcySunYang 文件遍历生成文档不全,只能便利获取第一个文件夹.vue文件 |
Please show your |
@HcySunYang .vueserc 如下 |
检查你上面的两张截图,你会发现 |
@HcySunYang |
首先生成文档时只关注一个组件的四个部分:slot、event、props 以及带有 export default {
components: {},
data() {
return {
collapsed: false
};
},
computed: {},
methods: {
// @vuese
menuBtn() {
this.collapsed = !this.collapsed;
}
},
mounted() {}
}; 为什么这么设计,文档中有说,请仔细阅读文档:https://github.com/vuese/vuese#write-a-document-for-your-component |
@HcySunYang 好的,明白了,还有几个体验不太好的问题如下: |
3.出现了文档显示错乱的问题。 |
这个问题需要优化,一个临时解决方案是:先在default选项上添加一个注释,用来代替原始默认值即可 |
等待优化版本 |
0 info it worked if it ends with ok
1 verbose cli [ 'd:\Program Files\nodejs\node.exe',
1 verbose cli 'd:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'gen' ]
2 info using npm@5.6.0
3 info using node@v8.11.3
4 verbose run-script [ 'pregen', 'gen', 'postgen' ]
13 verbose stack Error: egg-vue-boilerplate@1.0.0 gen:
vuese gen --include="app/web/**/*.vue"
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (C:\Users\H004335.WTOIP\AppData\Roaming\nvm\v8.11.3\node_modules\npm\node_modules\npm-lifecycle\index.js:285:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess. (C:\Users\H004335.WTOIP\AppData\Roaming\nvm\v8.11.3\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:925:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
The text was updated successfully, but these errors were encountered: