Just switches the order of module loading scenarios.
This change only has an effect on apps that are build with electron or nw.js in combination with the require.js optimizer. The problem with these apps is that they share the "require" statement of node.js with the front end, which then collides with the "require" statement of require.js.
Although it is possible to define a different namespace during r.js optimization, knockout and ko-projections will throw some funny errors.
This is only way I got it to work, combined with some other hacky stuff.
I fell in love with your yeoman generator for knockout and really don't want to switch to angular or any other hyped framework to be able to build electron/hybrid apps.
Just switches the order of module loading scenarios.
This change only has an effect on apps that are build with electron or nw.js in combination with the require.js optimizer. The problem with these apps is that they share the "require" statement of node.js with the front end, which then collides with the "require" statement of require.js. Although it is possible to define a different namespace during r.js optimization, knockout and ko-projections will throw some funny errors. This is only way I got it to work, combined with some other hacky stuff.
I fell in love with your yeoman generator for knockout and really don't want to switch to angular or any other hyped framework to be able to build electron/hybrid apps.