We at Bitovi love open source. We build powerful tools and open source them to support the community. We dedicate full-time resources to developing open source projects that help anyone build usable, performant, and maintainable web applications…
Lots of notable releases, community projects, and technical content was released in the DoneJS community last month! This post outlines some of the highlights from January 2017.
StealJS 1 has been released! It’s a major new version with some breaking changes, but our migration guide has everything you need to upgrade your app or plugin today.
Lots of notable releases, community projects, and technical content was released in the DoneJS community last month! This post outlines some of the highlights from December 2016.
StealJS 1.0 is here and represents an important milestone along its mission. This article reiterates that important mission, goes over a few of 1.0's most useful features, explains how to upgrade for 0.16 users, and looks ahead to what's coming on StealJS's roadmap. StealJS's mission is to make it cheap and easy to do the right thing. Doing the right thing, when building for the web, includes things such as writing tests and breaking your applications into smaller mini-applications (modlets) that can be composed together.
CanJS 3 has been released! It’s a major new version with some breaking changes, but our migration guide has everything you need to upgrade your app or plugin today.
Hello web devs! CanJS 3.0 is out. It has a new developer-centric website and new features like:
Existing solutions for server-side rendering your single-page application are full of compromises. These compromises affect the performance of your application (affecting the time until your user sees content) and the maintainability of your application (affecting how quickly you can iterate and bring more value to your user).
One of the most impressive parts of a DoneJS application is Server Side Rendering (SSR). You can write your code once and it will render both on an SSR-enabled web server and in the browser. You’ve probably noticed, while building your DoneJS app, that it’s a generally seamless experience. However, you’ll eventually run into a situation where the code on the server doesn't execute the way you would expect. Let’s take a look at why that’s the case, then I’ll show you a neat little DoneJS utility that makes it easy to debug these situations when they appear.