The first bit of news is that we now have the new documentation website. Wallaby.js docs have outgrown 'readme' file a long time ago, and it's something that we have been planning to do for a while. It should now be much easier to find everything you need. Also feel free to ask your questions in the docs comments.
The second piece of news is pretty exciting, especially if you have purchased or are planning to purchase a 'Freedom' license. Today I am happy to announce that we have started an active development of wallaby.js plugin for Atom code editor. The development is going pretty smoothly so far. I'll share some more progress and possibly the ETA in the next newsletter.
Last, but not least, a few smaller news and features.
- IntelliJ IDEA 15, WebStorm 11. IntelliJ IDEA 15 EAP has started, WebStorm 11 EAP is also not too far away and wallaby.js now supports the latest IntelliJ development branch. So just letting you know, if you'd like to start using IntelliJ IDEA 15 EAP now or WebStorm 11 EAP when it gets released, wallaby.js is already supported there.
- Visual Studio 2015 support. It's less than 2 weeks left before the next major Visual Studio release and I'm glad to mention that wallaby.js is already supported there and waiting for you, whenever you decide to move to the new version. If you don't have a copy of wallaby.js for VS 2015 yet, you may get the download link to your email from our website. If you will have to stay on VS 2013 for a while, don't get upset - we have added the support for the Update 5 RC as well.
- Assertion data diff viewer (IntelliJ platform). If you often find yourself making assertions about arrays, objects, and strings equality in your tests, you may find this new feature useful. It works for all testing frameworks that we support: Mocha plus Chai, Jasmine/Jest toEqual matcher, QUnit assertions.
- 'Run project tests' action. The action allows you to quickly run all of your tests to make sure that wallaby.js incremental runner didn't miss anything. It is faster than restarting wallaby.js and may be quite useful to run before committing your changes to your VCS.
You may also find more details about bug fixes and other features in our change log.
Thanks for reading, appreciate your feedback, stay tuned and follow us on Twitter to be the first to receive all the news.