Rave is definitely the future, so we're putting all of our effort into ensuring that RaveJS is as awesome as it can possibly be.

This means that all development for curl.js and cram.js has stopped. For the foreseeable future, we will continue to respond to issues on github, as well as in the #cujojs room on freenode. However, keep in mind that there will be no further development, so some issues might not be resolved fully.

We've added some info in the README, as well as some links to various RaveJS resources and a migration guide.

Watch rave to stay up to date!

Bug fixes for better compatibility with modules and task runners

@unscriptable unscriptable released this Mar 15, 2014 · 3 commits to master since this release

  • Fix module parsing code to stop prematurely detecting the end of an
    AMD define when there are regexp literals inside parentheses.
  • Only declare global define() during bundling to help isolate problems
    with UMD modules running under node (as with gulp and grunt).
  • Separate argument-parsing code from cramming code so logic to run
    as a module or as a command-line tool can be done more sanely.

Fixes to cram's JavaScript API

@unscriptable unscriptable released this Mar 11, 2014 · 8 commits to master since this release

  • Fix logic to detect whether cram is running as an npm task and ensure
    that the promise returned from the API only resolves once the bundle
    is created.
  • Stop appending to the cached AST data. It should be overwritten.

New JavaScript API allows integration with grunt and gulp!

@unscriptable unscriptable released this Feb 13, 2014 · 17 commits to master since this release

  • Add a minimal JavaScript API and documentation.
  • Correct regression: --exclude CLI option now works again.
  • Handle when factory args > dependent module ids when simplifying AMD defines.
    For instance, the curl/loader/cjsm11 cram plugin adds an extra arg now.

Bug fix

@unscriptable unscriptable released this Jan 23, 2014 · 23 commits to master since this release

  • Stop failing when plugins output more than one define().

More bug fixes

@unscriptable unscriptable released this Jan 17, 2014 · 25 commits to master since this release

0.7.11

  • Fix compile bug that prevented use of css! plugin.
  • Start using when.js 2.x.
  • Fix configuration merging errors when inspecting both html and run.js.

0.7.10

  • Ensure that baseUrl and output are converted to absolute paths so
    node doesn't try to resolve them using node_modules logic.

Force cram to use absolute paths to find all modules

@unscriptable unscriptable released this Dec 20, 2013 · 31 commits to master since this release

  • Ensure that baseUrl and output are converted to absolute paths so
    node doesn't try to resolve them using node_modules logic.

Bug fixes

@unscriptable unscriptable released this Dec 19, 2013 · 33 commits to master since this release

  • Bug fix: plugins are now responsible for resolving url/filepath.
  • Bug fix: Normalize r-value require()s when using loaders, too.
  • Bug fix: Infer appRoot from run.js file, not just index.html.
    Improve logged messages a bit, too.
  • Bug fix: Excluded modules don't get compiled anymore.
    Force 'curl' and 'curl/_privileged' to be excluded in all cases.

Fix #32 and #33

@unscriptable unscriptable released this Dec 19, 2013 · 39 commits to master since this release

Fix #32 and #33

Refactoring and bug fixes.

@unscriptable unscriptable released this Oct 15, 2013 · 42 commits to master since this release

  • Lots of fixes to the code that groks html files.
  • Internal refactoring and reorganization