First of all, I am happy to announce that today we are officially releasing wallaby.js Atom editor integration. During the last two months of the beta program we have received a lot of positive feedback. The integration have been tested by hundreds of our beta users, so we are pretty confident to proceed and start selling commercial licenses for it.
If you are a happy owner of wallaby.js 'Freedom' license and use the tool in Atom, you may just activate it with your license key.
If you are considering to purchase a 'Freedom' license or just a license for Atom - go ahead and do it today. However, if you need a bit more time to evaluate the tool or to plan your budget, you may use the extended license key, which you may find at the end of the email. The key will work for you until the 15th of November.
Just in case if you have missed the beta program of wallaby.js for Atom, but would like to give it a go, you may start with the official tutorial in our docs or this awesome article by Mark Kahn.
Now it's time for some more wallaby.js news and updates that you may find interesting:
We are expecting to share some more exciting news in a few weeks, so stay tuned and follow us on Twitter. That's it for the newsletter, thanks for reading.
- Wallaby.js can now run projects using TypeScript and Webpack/Browserify together.
- One of the scenarios where one may use the combo mentioned above is Angular 2 project and I'm happy to share the sample Angular 2 app where you may find a working wallaby.js config.
- Wallaby.js configuration has been officially included into the Aurelia skeleton app, so if you are using the framework and would like to run your tests with wallaby.js, you may have a look into the repo to get the idea how to configure it.
- If you use Browserify or Webpack, don't forget to keep updating your wallabify or wallaby-webpack package. We have made some improvements in both.
- If you use Karma/Mocha runner and wallaby.js, and would like to share your files/tests list between the runners to avoid any config code duplication, you may have a look into the TestRunnerConfig project by Frank van Wijk.
- Back to the land of TypeScript - wallaby now supports TypeScript 1.6 and TSX (JSX in TypeScript).
- Apart from tons of other improvements and bug fixes, we have also made (and keep making) several wallaby core improvements to better track dependencies between source code and tests for various scenarios. The goal is to keep wallaby restarts (or full test re-runs) to minimum. You may have already noticed some of the improvements.