When developing an app I have sencha app watch
running. This, of course, watches for file changes and triggers a development build. So now I can exercise the app under development in the browser. Nice.
The problem is a sencha app build testing
does not behave the same way as the Development build. The difference is in needing requires
. If a requires
is missing in Development, the app functions as if it was there.
Chrome throws a warning - sometimes:
[W] [Ext.Loader] Synchronously loading 'MyApp.view.Etc'; consider adding Ext.require('MyApp.view.Etc') above Ext.onReady
After a Testing build (or similarly after a Production build), those warnings become errors and the app does not function.
Yes, during development time one should ensure all requires
are added. But if I miss one I'm in trouble - the painful "but it works on my machine" syndrome.
This would not be a problem if either I could tell sencha app watch
to not be forgiving of missing requires
or to tell sencha app build testing
(or production
) to do what the Development build does and infer the missing requires
.
How can I make Development builds behave the same as Testing and Production?