I'm having this problem using the knockout.mapping plugin in conjunction with RequireJS. Basically, the site that hosts my app is loading knockout, knockout.mapping and requirejs in this order.
Without even doing anything further, I get this mismatch error. Is there some sort of order I'm failing to realize?
/// Update ///
I wrote these two tests:
Basically, what you see is that if I load require.js into my project on it's own, prior to the mapping plugin, then the mapping plugin becomes invisible. I assume this has to do with how the mapping plugin is using require to require knockout...but I can't nail down why it fails.
/// 2nd Update ///
It seems the scenario is important here, so I'm going to provide a bit more context.
Picture a web application which defines knockout.js and knockout.mapping.js in script tags. Then a third party widget loads into the page which uses requireJS to establish it's dependencies. It's that loading that seems to cause the issue. Since some libraries were loaded via the old school, manual way and others were loaded using require, require seems to mess with the context of the existing libraries.
If I remove the reference to require from the host application, I then get an error when I come back around to see if ko.mapping exists. This is clearly because the widget did a require on knockout which somehow broke it's relationship with the mapping plugin.
I think I need someone who is very familiar with RequireJS to comment on stacking these libraries. Obviously, when I'm creating a widget for anonymous consumption, I won't know how or if consumers are using requireJS.
/// 3rd Update /// Trying to clarify the issue as best as possible, maybe this will make more sense:
Is there any clearly defined pattern in which you could inject a widget, which uses RequireJS, into an existing web page, which loads resources manually? It would seem like it is impossible since RequireJS will just double load anything which the traditional page may have already loaded.