在sencha-cmd中使用“sencha app build`”和“sencha app watch`”命令的不同结果

Question

我用的是Extjs-6。我用sencha -sdk D:\xampp\htdocs\Lib\ext-premium-6.0.0\ext-6.0.0 generate app Prj1 D:\xampp\htdocs\ExtProjects\Workspace1\Prj1创建了一个应用程序。我使用sencha app build构建了这个项目，主题结果如下：

但是，当我使用sencha app watch构建项目时，它们的结果如下：

​

为什么结果是不同的

Answer 1

我不认为theme...For每两次都会有任何变化，当你和new ExtJS 6 default Triton theme在一起的时候。

如果需要更改主题，则通过将“packages/local/my-classic-theme/package.json”中的extend属性从其默认值中更改来完成，如下所示：

"extend": "theme-neptune"

至

"extend": "theme-crisp"

Answer 2

更新：

有一个bug与sencha app build和sencha app watch相关。你可以在森查论坛上的这篇帖子看到它

旧的答案：

对我来说，sencha app build似乎没有更新classic.json，所以必须执行sencha app watch。

我做了以下几件事：

$ sencha app build development
Sencha Cmd v6.1.2.15
[INF] Using GPL version of Ext JS version 6.0.1.250 from /home/alfonso/git/goraexplorer/src/main/webapp/ext.
[INF] The implications of using GPL version can be found here (http://www.sencha.com/products/extjs/licensing).
[INF] Processing Build Descriptor : classic
[INF] Loading app json manifest...
[INF] Appending content to /home/alfonso/git/goraexplorer/src/main/webapp/bootstrap.js
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/classic.json
[INF] merging 258 input resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer/classic/resources
[INF] merged 0 resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer/classic/resources
[INF] merging 21 input resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer
[INF] merged 0 resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/sass/example/bootstrap.json
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/sass/example/bootstrap.js
[INF] Appending content to /home/alfonso/git/goraexplorer/src/main/webapp/bootstrap.js
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/classic.json

$ cd ..
$ cp -R webapp /tmp/webapp-build

$ sencha app watch
Sencha Cmd v6.1.2.15
[INF] Using GPL version of Ext JS version 6.0.1.250 from /home/alfonso/git/goraexplorer/src/main/webapp/ext.
[INF] The implications of using GPL version can be found here (http://www.sencha.com/products/extjs/licensing).
[INF] Processing Build Descriptor : classic
[INF] Starting server on port : 1841
[INF] Mapping http://localhost:1841/~cmd to /home/alfonso/bin/Sencha/Cmd/6.1.2.15...
[INF] Mapping http://localhost:1841/ to /home/alfonso/git/goraexplorer/src/main/webapp...
[INF] Application available at http://localhost:1841
[INF] Loading app json manifest...
[INF] Appending content to /home/alfonso/git/goraexplorer/src/main/webapp/bootstrap.js
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/classic.json
[INF] merging 258 input resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer/classic/resources
[INF] merged 0 resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer/classic/resources
[INF] merging 21 input resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer
[INF] merged 0 resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/sass/example/bootstrap.json
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/sass/example/bootstrap.js
[INF] Appending content to /home/alfonso/git/goraexplorer/src/main/webapp/bootstrap.js
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/classic.json
[INF] Waiting for changes...
^C

$ cd ..
$ cp -R webapp /tmp/webapp-watch

$ diff -q -r /tmp/webapp-build /tmp/webapp-watch
Los archivos webapp-build/classic.json y webapp-watch/classic.json son distintos

(classic.json更改)

这是差异。如您所见，sencha app watch定义了一个"loadOrder“键，这很可能是应用程序中的差异所在：

​

​

如果浏览器(F12)显示加载文件的任何错误，您可以使用它的开发工具进行检查。请注意，如果您再次执行sencha app build，classic.json中的更改将再次错误地写入。

真正的问题肯定是在装载机的某个地方，但我认为我们无法修复它:/