Understanding r.js w / grunt & basebone options and relative paths

Question

I am trying to figure out how to use r.js. I keep getting errors that occur in such a way that the module path does not exist, or files that are dumped where they should not be.

I have a one page application integrated with wordpress. I accepted this template pattern for my overall structure, although I installed a completely different one. Below is my file structure.

.Theme Folder
├── _assets
|   ├── _application
|   |   ├── css
|   |   ├── fonts
|   |   ├── img
|   |   ├── _js
|   |   |   ├── main.js  //this is my require.js config file
|   |   |   ├── _app  //here where the boilerplate structure comes into play
|   |   |       ├── collections
|   |   |       ├── models
|   |   |       ├── routers
|   |   |       ├── templates
|   |   |       ├── views
|   |   |   ├── libs
|   |   |   ├── utilities
|   |   ├── scss
|   |   ├── video
|   └── build  //Concatenated application directory mirror
|   └── gruntfile.js
|   └── bower.json
|   └── package.json

grunt. , conatenated, . r.js, . , lodash ( main.js). , lodash /lodash.js, baseUrl main.js(configuration.js). - /application/js/libs/lodash.js. requirejs :

        requirejs: {
          compile: {
            options: {
              baseUrl: "./",
              mainConfigFile: "application/js/main.js",
              name: "./application/js/main",
              out: "./build/js/optimized.js"
            }
          }
        }

, rjs. , , . , ... - , r.js, .

, :

>> Error: ENOENT, no such file or directory
>> 'path-to-theme-folder-here/assets/libs/lodash.js'
>> In module tree:
>>     application/js/main.min

Answer 1

, , :

requirejs: {
  compile: {
    options: {
      baseUrl: "application/js/",
      mainConfigFile: "application/js/main.js",
      name: "main",
      out: "build/js/optimized.js"
    }
  }
}