Uglifying a RequireJS/Backbone project into one single .js file?

Question

I worked along the following tutorial to try to optimize my project into one single .js file, but unfortunately I can't seem to get the expected results. I get r.js to create an optimized folder for me, but instead of a single file, I get uglified copies of each individual .js file in their respective folders. Seems like that last concatenation step is somehow missing.

I'm trying to leverage an existing config file instead of using paths, I don't know if that specific step is breaking it.

My build/app.build.js is:

({
  appDir: '../',
  baseUrl: 'js',
  mainConfigFile: '../js/config.js',
  dir: '../../my-app-build',
  modules: [{
    name: 'main'
  }]
})

My main.js file has the config file as its dependency:

require(["config"], function() {
  require(['underscore', [...]
    [...]
  }
}

And the config file is where all of my project dependencies are declared:

require.config({
  baseUrl: "js",
  paths: {[...]},
  shim: {...]},
});

Does anyone have insight into why I might not be getting that single file output that I'm looking for? I tried the other approach in this post, but that only ever produces main.js for me with the config file prepended to it.

Thanks!

score 3 · Accepted Answer · answered May 14 '13 at 04:23

The issue was caused by the following option missing from the r.js build configuration file:

findNestedDependencies: true

Without it, r.js would not go past the first require in main.js, thus loading only config.js and none of the next level of dependencies. Just for reference (note that it saves the product of optimization in the same source folder, which is not ideal) looks like this:

({
  baseUrl: '.',
  mainConfigFile: 'config.js',
  name: 'main',
  out: 'main-build.js',
  findNestedDependencies: true,
})

score 1 · Answer 2 · answered May 13 '13 at 04:38

1

I had the same problem and got the solution from the Github Issue list. May be this configuration parameters will help you too

https://github.com/jrburke/r.js/issues/379

If you only want one JS file built, instead of using dir: use out: for a single JS file build.

answered May 13 '13 at 04:38

Deeptechtons

10,945
27
96
178

Do you happen to have a sample build config file that worked for you? That'd be really helpful. – Alexandr Kurilin May 13 '13 at 04:42
It is present in my projects repository on Github https://github.com/deeptechtons/BackboneGarage/blob/master/Widget/build.js – Deeptechtons May 13 '13 at 05:20
Is mainConfigFile interchangeable with paths, or do paths always have to be present? It would feel like duplication to me if I were to copy and paste what's already in my config file. – Alexandr Kurilin May 13 '13 at 05:39
@AlexandrKurilin It is interchangeable with paths – Deeptechtons May 13 '13 at 06:10
appreciate the link, very helpful for my own reference! I found the answer tangentially. – Alexandr Kurilin May 14 '13 at 04:23

score 0 · Answer 3 · answered May 13 '13 at 00:48

0

Specify output filepath:

({
    // ...
    out: '../main.min.js'
})

answered May 13 '13 at 00:48

Tomas Kirda

8,347
3
31
23

Uglifying a RequireJS/Backbone project into one single .js file?

3 Answers3