Thank you for reporting this bug. We will make it our priority to review this report.
-
Sencha Premium Member
Compile to Production Issue
Issue
Build Web App for Production produce package not runnable when include an external js resource.
But if set for Testing, the compile web app works fine.
I was using SA 4.2.1 with CMD 6.5.0. But just upgrade to SA 4.2.2 with CMD 6.5.1 but produce the same results.
To reproduce
1. Create a blank project
2. Add a panel and button
3. Add a resource "Config.js" and set requireSdk and disable IncludeInBundle
Ext.define('MyApp.Config', {
statics: {
baseUrl:'http://example.com'
}
});
4. Build Web App for Production
Observation
The Config.js file seems to contain the entire EXTJS framework
-
Sencha User
This functionality of SA is fully based on Cmd. You can observe the same behavior when you create and build the app without SA. I do not know if it is bug, but you can ask in Cmd forum to get more info.
-
Sencha User
The production build does not add to your js file whole framework, but only ES6 polyfills.
-
Sencha Premium Member
Thanks for the info.
The Config file becomes invalid because of the polyfil. Is there a fix?
-
Sencha User
Could you share more details, please? What does the invalid means?
-
Sencha Premium Member
It is going to be tough to look up at the Config.js file with all the polyfills.
Screen Shot 2017-08-03 at 3.50.45 PM.jpg
when my Config.js suppose to a few lines
Screen Shot 2017-08-03 at 3.53.16 PM.png
When compile set for testing the Config.js doesn't contain ES6 polyfills.
The Config.js needs to be visible and easily editable to change the configuration.
-
Sencha User
Could you ask in Cmd forum or support portal if there is possibility to turn off inserting polyfills in production build, please?