StealJS 2.0 is out and available on npm! 🎆 Check out the migration guide to help you upgrade.

The humble DoneJS core team enthusiastically presents CanJS 5.0. Like 4.0 before it, this release continues to simplify CanJS and solve problems in new and ergonomic ways. If you are unfamiliar with CanJS, the common web development problems it tackles are:

• Responding to user interactions and updating HTML with components (custom elements).
• Retrieving and modifying service data with models.
• Routing url changes to state changes and state changes to url changes with routing.

Driven by community feedback, CanJS 5.0 focused primarily on making CanJS easier to use and learn in modern development environments and improving the model layer. Yet, we still managed to improve components, routing and even testing with one new feature.

In our first community survey, making it easier to configure and understand can-set was one of the top-voted items. We’re excited to deliver on that proposal in CanJS 5, which will include the following new modules that are easier to understand and configure:

One of the most highly-voted on items from our March community survey was making CanJS tree-shakable, and it’s now available in CanJS 4.2!

CanJS 4 and DoneJS 2 are out! Check out those blog posts for the full details on the new:

• debugging tools (hello can-debug)
• streaming property definitions (goodbye listening to {viewModel} events)
• cli commands: donejs add heroku, travis, travis-deploy-to-firebase, & travis-deploy-to-heroku

DoneJS now features improved error handling and messaging for those on donejs@2. In recent weeks we have added:

The core team has been focusing our attention on shipping CanJS 4.0, which will make CanJS easier to debug with queues for error-free and traceable code.

We’ve made a lot of progress on the highest-voted items from the community survey in September.