Managing the require.config.js file? #95

Closed
eclifford opened this Issue Nov 20, 2012 · 7 comments

4 participants

@eclifford

I love the idea of JamJS but what is bothering me is that every time I add a library the require.config.js is overwritten. I can't seem to find a good strategy as to how to handle customizations to the require-config file such as baseUrl, timeout, shims and aliases for non AMD or even AMD libraries not in JamJS. Obviously I could create two separate config files one for my Jam deps and one for everything else but that just feels wrong.

Has anyone found a more elegant solution to this problem?

@caolan
Owner

use jam's require.js file and then just configure by doing require.config({...})

@eclifford

@caolan so basically two config files right? Or Jam's require config and an inline require.config block. I guess there is nothing wrong with that I'm just trying to centralize my configurations.

@caolan
Owner

Yes, maintain your own config separate from Jam's config.

@eclifford

Cool thanks :)

@metmajer

Doesn't an implementation where require.config.js gets generated if it does not exist and otherwise does not get touched make more sense? The re-generation of both require.js and require.config.js are misleading in my opinion since both of them define their own configuration blocks.

@caolan: your opinion on that? Thanks!

@nfriedly

What about when I run jam compile? Right now it's failing on paths that are defined in my require.config() call. (It is including the file with the require.config() call, but it's not executing it to get the config info.)

@caolan
Owner

closing this in favour of #127

@caolan caolan closed this Feb 5, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment