calling buildProduction on front end using requirejs fails about assetgraph-builder HOT 8 CLOSED

Thanks for the detailed report. I know there are some race conditions where the require.js configuration won't yet be extracted at the time when the require/define calls are resolved. Could you try defining the require.js config in an inline script in your HTML instead using this syntax?

<script>
    var require = {
        paths:
            backbone         : 'vendor/backbone-amd/backbone' 
            deepmodel        : 'vendor/deep-model'
            ...
    };
</script>
<script src="/js/vendor/requirejs/require.js" data-main="/js/app"></script>

from assetgraph-builder.

That's a lot of stuff to jam into the index file. It's a sizable app. Can the race conditions be fixed? Based on the numerous examples Ive seen, this is a very common way apps are set up. If requirejs compatibility is a goal, this is important IMO.

from assetgraph-builder.

I agree, and it's certainly on my list. I asked you to try the above so I'd know whether this is a separate issue.

from assetgraph-builder.

Fair enough. Ill wire it up and let you know what happens

from assetgraph-builder.

Hmm, that turned out not to be the problem. I've created a stripped-down test case based on your description, and it does indeed look like the module names aren't resolved relative to your data-main module. I'm working on a fix. In the mean time you can avoid the bug by using an explicit baseUrl setting:

require.config {
    baseUrl: '/js'
    paths:
        backbone         : 'vendor/backbone-amd/backbone' 
        deepmodel        : 'vendor/deep-model'
        ...
}

from assetgraph-builder.

@papandreou sorry I didn't get to the test before you did. the baseUrl does indeed bypass the problem for now. Thanks!

from assetgraph-builder.

No prob, had all the info I needed in your report. Fixed in 1.7.5.

from assetgraph-builder.

nice!

from assetgraph-builder.