Connective intelligence https://git.yuv.al/rhizi/atom/tests/output/test_sub_process.js.stdout?h=graph-view-commit-log 2014-10-27T13:47:39Z 2014-10-27T13:47:39Z Alon Levy alon@pobox.com 2014-10-27T13:47:39Z urn:sha1:7c974d834b7c6f0e3a0cf1f3d06b97ffc436ec36 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.