Add an option to split output into sencha and app code

mattgoldspink / grunt-sencha-dependencies

Grunt task to get the list of Ext.require dependencies in your application

MIT License

32 stars 22 forks source link

Add an option to split output into sencha and app code #13

Closed cburgdorf closed 11 years ago

cburgdorf commented 11 years ago

Currently we write all files into one file. Sometimes you may want to have two output files. One with all the Sencha dependencies and one with all the other dependencies. This way you can quickly see how much of the bytes is from Sencha and how much from us etc.

I guess we could simply say, everything within the namespace "Ext." is a Sencha dependency. Or maybe better: Everything that is Ext but also not Ext.ux. Also Sencha discourages you to use Ext.ux for plugins, most plugins still use this namespace.

netmiller commented 11 years ago

+1 for that. Very useful.

mattgoldspink commented 11 years ago

The plan for this is to create 3 properties:

sencha_dependencies_{task}_ext_core - only core Ext files (anything that came from the directory senchaDir)
sencha_dependencies_{task}_app - all none ext core files
sencha_dependencies_{task} - all of the above combined in the correct order

mattgoldspink commented 11 years ago

This is now available in 0.6.0