javascript - Why is Dojo build generating all it's dependencies next to the released dojo.js file? -
all want bundled version of dojo require loader, domready, , query , nothing else. have tried many release.profiles , experimented changing config.
i tried these too: http://dojotoolkit.org/reference-guide/1.8/build/custombase.html http://jamesthom.as/blog/2012/08/03/finding-nano/
this , many other examples generate whole folder of dojo , files next dojo.js file. past few weeks of experimentation didn't realise dojo.js file built version. it's bit difficult know since it's sitting next other dojo files. version of dojo? i'm using 1.8, latest java 32 bit installed on version of windows 7.
any appreciated. thanks
dojo generate output layer file in output directory - you've discovered - because need modules aren't mentioned in layer file can still occur @ runtime, dojo packages other input files output directory they're available on demand.
(it can optionally minify layer files , standalone files, separately.)
having said that, don't have use on-demand files:
i've never managed find way stop doing copy/transform, i
- generate layer files (being careful ensure can't possibly need other modules @ runtime)
- throw away other files
it can bit fiddly ensure layer files complete, you're talking small set, should okay case.
i don't believe there's sort of straightforward way stop dojo generating them in first place, unfortunately.
Comments
Post a Comment