Skip to content

Releases: BladeRunnerJS/fell

Enhanced Backwards Compatibility

24 Sep 09:31
Compare
Choose a tag to compare

Make fell backwardly compatible with the 0.0.x API.

Improved Mocking Framework Compatibility

16 Aug 08:18
Compare
Choose a tag to compare

The onLog() callback now provides a proper array, rather than an argument array, so that mocking frameworks used for testing (e.g. Sinon.JS or JsMockito) now work correctly.

IE8 Support

07 Aug 07:03
Compare
Choose a tag to compare

IE8 is now working again, and we now have our automated test suite running against IE8 on every check-in so we can ensure continued compatibility in the future.

Simplified API

04 Aug 17:05
Compare
Choose a tag to compare

We've simplified the fell API so that you get direct access to the logger, and so that you are no longer obliged to use JsHamcrest for testing.

Library Standardization

31 Jul 11:20
Compare
Choose a tag to compare

Made a number of changes to make the library more consistent with other typical NPM libraries:

  1. Use karma, mocha & expectations instead of jasmine for testing.
  2. Use browserify instead of webbuilder for building.
  3. Use eslint for linting.
  4. Use npm instead of Grunt as our build tool.
  5. Use standard directory names: lib -> src, spec -> test & target -> dist.
  6. Use npm test for running all tests, including a locally run browser test against Firefox, and SauceLab tests against various other browsers.
  7. Stop using jsdoc, and use example driven README.md based documentation only.
  8. Stop creating browser-modules compatible distributions of our libraries, that even we don't use.
  9. Use a master branch instead of a gh-pages branch for simplicity, and get rid of the extra styling, and links to the different presentations of the exact same content.
  10. Use : as a delimiter to indicate sub-tasks.
  11. Stop using browser detection guards within code and tests, and instead let browserify provide a consistent environment.