The best way to package an aura project about aura HOT 9 CLOSED

I'd say all of them are good options, and the best approach would depend on the project. For the main product at the company I work at, for example, I'd like to adopt the 1).

from aura.

imo, 1) probably works best for quite a few scenarios.

from aura.

Has anybody an example for optimizing a widget into a single file via grunt? I tried a couple of options but I'm stuck. Would be great if someone could share an example

from aura.

Thank you @gersongoulart and @addyosmani for the response.

@DigitalHero i've investigated some options to build it like option 1) and here is a dirty wip snippet from my grunt:requirejs config - you might have to change the the src path:

modules: (function(){
            var fs = require('fs'),
                src = './js/widgets',
                output = [];

            //Add the main file
            output.push({
                name: 'app',
                include: [ 'text' ]
            });

            fs.readdirSync(src).forEach(function(dirName){
                output.push({
                    name: 'widgets/' + dirName + '/main',
                    exclude: ['sandbox', 'text']
                });
            });

            return output;
        })(),
        removeCombined: true

from aura.

Thanks @henrikkok, your snippet works great. I think this should be included in the aura grunt.js

from aura.

@dustinboston what do you think about us including this in our grunt file by default?

from aura.

@DigitalHero glad it helped :-)
@addyosmani I can create a pull request, if the build process gets fixed (it's breaking atm).

from aura.

Thanks @henrikkok. I'll see what I can do to fix the build process tonight.

from aura.

@addyosmani Yes. That's perfect. We should document that the convention of main.js is a requirement for the build process. @henrikkok Nice work. Looks great.

from aura.