Skip to content
Commits on Jul 17, 2012
  1. Don't move so fast, sir! Beware that copy and paste. Oh dot three dot…

    committed Jul 16, 2012
    … four.
    
    * Copy/paste bug fix.
  2. v0.3.3

    committed Jul 16, 2012
Commits on Jul 11, 2012
  1. v0.3.2

    committed Jul 11, 2012
Commits on Jun 27, 2012
  1. v0.3.1

    committed Jun 27, 2012
Commits on Jan 10, 2012
  1. Tackle issue #2. Removed hard node restrictions. Oh dot three dot oh.

    committed Jan 8, 2012
    * Removing minor version requirements for nodes; this means that new node
      releases have the potential to break autorequire, however unlikely.
    * Given that module.js has been stable for a good amount of time now, and
      that node versions rev so frequently, I'm switching policy.
    * Introducing a testedEngines field into package.json that indicates which
      nodes have been tested (and get run by test-all)
    
    See #2 for a discussion about this (and me flip-flopping on the issue).
Commits on Jan 8, 2012
  1. Minor README tweak. Build status moved to title. The layout matters.

    committed Jan 8, 2012
    * Move the Travis CI build status icon into the title of the readme for better flow.
Commits on Dec 21, 2011
  1. Minor version bump. With node oh dot six dot six. Oh dot two dot ten.

    committed Dec 20, 2011
    * Support for node v0.6.6
Commits on Dec 7, 2011
  1. Fixing engine deps. npm is finicky. oh dot two dot nine.

    committed Dec 6, 2011
    * Changing the engines version declaration to be npm-friendly.
    * Removing groc as a dev dependency so that travis doesn't freak out.
    * Also, bump to nodes v0.6.5, as we have nothing breaking.
  2. Using groc now. Docco doesn't quite cut it. Better docs abound!

    committed Dec 6, 2011
    * Switching away from docco to groc, which better supports more complex
      hierarchies of source files, and github pages publishing.
  3. Special-case naming. Override module names! Hastily added.

    committed Dec 6, 2011
    * A quick addition to conventions for overriding module names via a
      specialCaseModuleNames options object.
Commits on Nov 22, 2011
  1. Woo, Travis CI! Support for the latest nodes. oh dot two dot eight.

    committed Nov 18, 2011
    * Adding support for node v0.6.1 & v0.6.2.
    * Travis CI configuration.
    * Fixed tests to be independent of file system ordering.
    * Fixed the gitignore to include some missing test files.
    * Rebuilt lib with a more recent coffee-script, and pinned the
      version of it to 1.1.3 for stable sources.
Commits on Nov 10, 2011
  1. Some workflow cleanup. Prepublish is now scripted. Don't forget a thing!

    committed Nov 9, 2011
    * Prepublish script that ensures that we have everything built and in a
      happy state.
  2. Lazy load it all. The full lazy loading suite! dot two dot seven.

    committed Nov 9, 2011
    * We now expose ancestors to a module.
    * If there are any ambiguous ancestors (conflicting with globals or siblings),
      it is considered an error, currently.
Commits on Nov 6, 2011
  1. __path should be __dirname. In the name of consistency. oh dot two do…

    committed Nov 6, 2011
    …t six.
    
    * Module groups expose __dirname instead of __path, to be more consistent
      with Node proper.
  2. docco is so great. Documentation cleanup. Life is much better.

    committed Nov 6, 2011
    * Lots of cleanup to provide clearer in-line documentation.
  3. Complete Node compat. Now behaves like current Node. oh dot two dot f…

    committed Nov 6, 2011
    …ive.
    
    * Loader now mirrors behavior appropriate to the current Node version.
    * Adding support for v0.6.0
  4. Ohmai, it's a bug. Properly print test results. Confidence restored!

    committed Nov 6, 2011
    * The test-all runner was reading individual node results backwards.
      Fails now fail, as you would expect.
  5. Sandbox and shovel. Comprehensive loader tests. Time to dig it in.

    committed Nov 6, 2011
    * Explicit tests for Loader to ensure that we are properly defining
      the global properties that Node promises.
    * One test fails for nodes v0.5.2+ (missing a deprecation notice for
      require.paths)
  6. Must... test... everything! Can test all supported nodes. My chai is …

    committed Nov 5, 2011
    …tasty.
    
    * npm run-script test-all: Installs all missing node versions that the project
      cares about, and then runs tests for them.  Requires nvm to be installed.
Commits on Oct 31, 2011
  1. Underscores begone. Unbalanced like node proper. Mmm, consistency.

    committed Oct 30, 2011
    * Renamed all special properties for modules to only have __ at the beginning,
      rather than __name__.  Better follows the node style.
  2. Support oh dot five. Can't call regexes no more. oh dot two dot four.

    committed Oct 30, 2011
    * /some regex/(string) doesn't look supported any more, switching back to string.match()
    * Expanding node version support to the v0.5.* line as well.
Commits on Oct 30, 2011
Commits on Oct 24, 2011
  1. More introspection. Module group factory. Oh dot two dot two.

    committed Oct 23, 2011
    * Removing walkDirectory and replacing it with ModuleGroupFactory.
      * It's more complex, but allows for better overriding of behavior.
      * It also exposes a few special properties for module introspection.
    * Conventions now build the root module group for more behavioral control.
  2. Util refactor. Moved to their own module. Quite a bit cleaner.

    committed Oct 23, 2011
    * Moved lazyLoad and getCallingDirectoryFromStack to a utils module.
  3. Module to test. Adding some variety. Makes me quite happy.

    committed Oct 23, 2011
    * Added a root level module to the mixed_tastes example module to ensure that
      modules + module (sub)groups are properly tested.
Commits on Sep 26, 2011
  1. Bugfixes abound. Convention hashes now work. Oh dot two dot one.

    committed Sep 25, 2011
    * Convention hashes actually work as documented.  Refactored argument processing.
    * Added tests and examples around that.
    * Lazy-loaded globals now honor the module's require instead of autorequire's copy of it.
      This ensures that you can properly load non-system dependencies as you would expect.
Commits on Sep 24, 2011
Commits on Sep 5, 2011
  1. scripts/test-all now in. More supported node versions! Oh dot one dot…

    committed Sep 4, 2011
    … two.
    
    * Test runner that tests all support Node.js versions - and putting down initial support for
      v0.4.3 - v0.4.11.
Commits on Aug 27, 2011
  1. Testing the good stuff. Conventions get us going. It is a good start.

    committed Aug 27, 2011
    * Two simple example packages to test from
    * Basic coverage for the three built in conventions
    * Some refactoring and bootstrapping of the tests
  2. Perhaps a bit green. It works like require now! Fixed like a ninja.

    committed Aug 26, 2011
    Yeah, so, autorequire only really worked if you were autorequiring a package from its root.
    
    Not exactly the desired use case.  Well, it works as expected now; respecting the path of
    the script that is calling autorequire.  If you're in a REPL, it uses the current working
    directory.
Something went wrong with that request. Please try again.