Already have a build.js file

[CMCDragonkai]

If I already have a build.js file, is it possible to point to that file as the configuration rather than setting it up in the Gruntfile. Currently I'm using a shell operation and simply doing -o.

[gnrlwart]

You can read in the file and add it into your grunt config like this:

  var buildOptionsFile = grunt.file.read( buildOptionsPath );
  var buildOptions = eval( buildOptionsFile );
  // ... Adjust path settings appDir, baseUrl, and mainConfigFile if needed
  gruntConfig.requirejs = {
    compile : {
      options : buildOptions
    }
  };

Just make sure you do this before calling grunt.initConfig( gruntConfig ).

[dminkovsky]

This is sweet. Maybe link this from the README?

[tkellen]

There is no need to do this incantation, r.js has a setting for specifying a build file: mainConfigFile

[dminkovsky]

Right, but if you're coming to grunt-contrib-requirejs from CLI usage, you already have a "build.js" file, which in turn is pointing to your mainConfigFile. You then have to replicate that build.js in your Gruntfile setup for grunt-contrib-requirejs.

[dminkovsky]

Which is no biggie, but all copy/pasting is annoying, especially when it might relate to build/deploy.

[Blasz]

mainConfigFile has to contain a requirejs({}), require({}), requirejs.config({}) or require.config({}).

build.js files should be JSON wrapped in parentheses and therefore cannot contain the require constructs that mainConfigFile needs.

Therefore mainConfigFile is not correct for specifying build profile files that you would pass via the command line to requireJS.