Connective intelligence https://git.yuv.al/rhizi/atom/tests/output/test_require_js.js.stdout?h=master 2014-12-16T15:37:42Z 2014-12-16T15:37:42Z Alon Levy alon@pobox.com 2014-12-16T15:37:42Z urn:sha1:ade19de410e0a789a921ec1666b278b2a64176d6 2014-11-13T15:41:57Z LV-426 lv-426@taproot.org.il 2014-11-13T15:41:57Z urn:sha1:76d1de512a58f023ae348ae8500100490fba9915 2014-10-20T18:36:37Z Alon Levy alon@pobox.com 2014-10-20T10:25:32Z urn:sha1:c919c4bfef4ad9e2dc25d040c0727dd29ad541ae Yes, I'm being lazy. The purpose of require.js is to allow writing modules, i.e. individual smaller then the whole files with clear dependencies. This is achieved by using a new api provided by require.js: define, require, requirejs Read more at [requirejs] (http://requirejs.org) Tests have been rewritten to work correctly with require.js; they still use jsdom. Test output is now stored in the repository, all tests are run via run_tests.js; This is a hack - once a good harness (with assertions, suites - unittest like) presents itself it will be used. Hidden here is also using FileSaver for history saving, so history is saved to history.json instead to a random name. Plus dropping some dead code.