Releases: dchambers/iterizerjs
Releases · dchambers/iterizerjs
Faster IterizerJs
Reliability & Polish
The following issues were fixed as part of this release:
- The string filtering methods described in the documentation now actually work as they have been properly tested.
- Negated filtering is now allowed using a
not
prefix. - The
install()
andinstallGlobals()
methods no longer globally install the installation methods themselves. - It's now genuinely possible to use IterizerJs without invoking
install()
orinstallGlobals()
-- onlyinstallMethods()
is needed for sensible usage of IterizerJs. - The Jasmine tests were split into three distinct test suites, which has allowed us to re-enable a slow test in the Project Euler suite, and test that IterizerJs can be used without installing any globals.
- The
npm test
command now runs all three of the Jasmine test suites, plus the main spec tests in Firefox and Chrome using Karma. - Updated the
npm test
command to now correctly return a non-zero exit-code if any tests fail so the build will show as failing in Travis. - Improved the directory structure and file names, so that the IterizerJs source code is easier to navigate.
- The tests are now run on Firefox and Chrome in Travis too.
- Updated the code blocks in all IterizerJs documentation to provide better syntax highlighting.
Better Documentation
There is now improved documentation at all levels:
- Introductory Blog Post
- README Page
- Web Site
NPM Build, Test & Publish Commands Working
The first release with properly built and tested artifacts.
NodeJs Dependence
IterizerJs is now developed using NodeJs with browserify being used to create UMD modules that can be used everywhere.
Initial Release
The first release of IterizerJs.