t.equal( require("./shared")(), 1, "the main app bundle can already use the shared library" ); t.throws(function() { require("./lazy"); }, "lazy bundle is not executed yet so the lazy module cannot be required yet"); // Use setTimeout as script loader simulator as in real use case this would be // a call to one. Now we just let the rest of the source code string we build // to execute. setTimeout(function() { // After lazy bundle is executed we can require the lazy.js module require("./lazy"); t.equal( require("./shared")(),3, "lazy module was able to use shared code" ); }, 1);
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 19553 | swellard | Move and rename clients | ||
//guest/perforce_software/helix-web-services/main/source/clients/2016.1.0/javascript/node_modules/browserify/test/reverse_multi_bundle/app.js | |||||
#1 | 18810 | tjuricek |
First-pass at JavaScript client SDK. JavaScript requires Node with Gulp to "browserfy" the library. It's the easiest way I found to use the swagger-js project; bundle up a wrapping method. There is no JavaScript reference guide. The swagger-js doesn't really document what they do very well, actually. Overall I'm not particularly impressed by swagger-js, it was hard to even figure out what the right method syntax was. We may want to invest time in doing it better. This required setting CORS response headers, which are currently defaulted to a fairly insecure setting. |