imouou/buijs-cli

BUI 开发包命令行生成工具

Hi there 👋

BUI：https://www.easybui.com/

BUI 是基于jQuery4或者Zepto的Webapp UI组件开发框架，双向状态管理，路径式路由和动态组件加载，丰富的模板生态资源，开箱即用零配置，一次开发跨平台、完美嵌入企业微信、小程序、公众号、钉钉、link等平台或通过Cordova、Dcloud、鸿蒙、Flutter打包独立 APP。

BUI is a Webapp UI component development framework based on jQuery or Zepto, with bidirectional state management, path-based routing and dynamic component loading, rich template ecological resources, and zero configuration out of the box

特点

• 开箱零配置：一行代码构建即可构建工程开发
• 高性能视图：每个组件按需加载，无需拆包。
• 跨平台适配：一次开发，跨平台全适配
• HTML模板：传统HTML，JS，ES模板一看就懂
• 模块化：支持AMD异步模块，全局模块，ES同步模块
• 轻组件：轻量路径式组件，按需加载，可单独预览调试
• 数据驱动：通过数据跟视图的绑定关系，自动更新（无虚拟Dom）
• 单/多页路由：单页SPA零配置路径式路由、传统多页面路由，简单高效
• less/sass：支持常用样式编译，默认为less
• 高保真还原：等比还原设计稿，应对不同手机分辨率下的适配问题
• 多种引用：支持NPM引入，Script传统引入，方便嵌入第三方

BUI 性能测试 ｜ BUI Demo演示 ｜ 在线开发-百搭模板构建

buijs-cli's Issues

默认的模板目录能否换成webpack打包，而不是gulp？

cli工具执行buijs create demo3报错如下

/usr/local/lib/node_modules/buijs/buijs-cli.js:387
package.scripts[dev-${name}] = cross-env NODE_ENV=${name} gulp dev;
^

TypeError: Cannot set property 'dev-demo3' of undefined
at modifyPackage (/usr/local/lib/node_modules/buijs/buijs-cli.js:387:52)
at /usr/local/lib/node_modules/buijs/buijs-cli.js:299:17

npm run dev 报错

events.js:183
throw er; // Unhandled 'error' event
^
Error: ϵͳ�Ҳ���ָ����·����

at notFoundError (D:\code\demo\node_modules\cross-spawn\lib\enoent.js:11:11)
at verifyENOENT (D:\code\demo\node_modules\cross-spawn\lib\enoent.js:46:16)
at ChildProcess.cp.emit (D:\code\demo\node_modules\cross-spawn\lib\enoent.js:33:19)
at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ dev: gulp dev
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ dev 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\AppData\Roaming\npm-cache_logs\2018-12-14T01_01_29_677Z-debug.log

---------------------------log 文件内容-----------------------------------------

0 info it worked if it ends with ok
1 verbose cli [ 'D:\download\node\node.exe',
1 verbose cli 'D:\download\node\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'dev' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle @~predev: @
6 info lifecycle @~dev: @
7 verbose lifecycle @~dev: unsafe-perm in lifecycle true
8 verbose lifecycle @~dev: PATH: D:\download\node\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;D:\code\demo\node_modules.bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;D:\download\node;D:\download\tortoiseGit\bin;D:\download\Git\cmd;C:\Go\bin;C:\Users\Administrator\AppData\Roaming\npm;%GOPATH%\bin
9 verbose lifecycle @~dev: CWD: D:\code\demo
10 silly lifecycle @~dev: Args: [ '/d /s /c', 'gulp dev' ]
11 silly lifecycle @~dev: Returned: code: 1 signal: null
12 info lifecycle @~dev: Failed to exec dev script
13 verbose stack Error: @ dev: gulp dev
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (D:\download\node\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. (D:\download\node\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)
14 verbose pkgid @
15 verbose cwd D:\code\demo
16 verbose Windows_NT 6.3.9600
17 verbose argv "D:\download\node\node.exe" "D:\download\node\node_modules\npm\bin\npm-cli.js" "run" "dev"
18 verbose node v8.11.1
19 verbose npm v5.6.0
20 error code ELIFECYCLE
21 error errno 1
22 error @ dev: gulp dev
22 error Exit status 1
23 error Failed at the @ dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

npm run dev 出错

npm -v ==》6.1.0
node -v ==》v10.6.0

npm run dev

@ dev /opt/www/p75ui
gulp dev

fs.js:119
throw err;
^

Error: ENOENT: no such file or directory, scandir '/opt/www/p75ui/node_modules/node-sass/vendor'
at Object.readdirSync (fs.js:759:3)
at Object.getInstalledBinaries (/opt/www/p75ui/node_modules/node-sass/lib/extensions.js:129:13)
at foundBinariesList (/opt/www/p75ui/node_modules/node-sass/lib/errors.js:20:15)
at foundBinaries (/opt/www/p75ui/node_modules/node-sass/lib/errors.js:15:5)
at Object.module.exports.missingBinary (/opt/www/p75ui/node_modules/node-sass/lib/errors.js:45:5)
at module.exports (/opt/www/p75ui/node_modules/node-sass/lib/binding.js:15:30)
at Object. (/opt/www/p75ui/node_modules/node-sass/lib/index.js:14:35)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ dev: gulp dev
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ dev 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! /root/.npm/_logs/2018-07-15T23_42_21_204Z-debug.log
这是啥问题？

模块加载问题

使用router.loadPart加载局部模块，底部导航mian.js中的mod.init()；报错，打印mod为空