Lots of notable releases, community projects, and technical content were released in the DoneJS community last month! This post outlines some of the highlights from September 2017.
I’m super exited about CSS grid, because finally there will be a way to layout pages and achieve more interesting and dynamic results, without a ton of code! So since I fell in love with Atom IDE recently (I know, I’m late to the party, but really I like it 😺), then it’s no surprise that I will be using it for this example on using CSS grid for layout.
At Bitovi, we’ve built a few projects with React, and we like its straightforward API and using JSX for templates. Redux is common in the React community, and we know it’s not the right solution for every project.
CanJS, for better or worse, allows a near endless variety of design choices. If you like MVC, MVVM, centralized state management, etc, you can build your app that way. Enabling this level of flexibility is difficult, especially because we don’t know what sorts of things people might want to integrate into CanJS.
The DoneJS team wants to hear from you. What do you love and hate about CanJS, DoneJS, and StealJS? What can the core team work on to make you grow fonder of these projects?
In this article we will: Learn why stateful packages challenge stability See an example of a stateful package Identify CanJS’s stateful packages Provide strategies that minimize the problems with stateful packages
The DoneJS core team has been experimenting with HTTP/2 for the past several months and the outcome is strong HTTP/2 support in DoneJS! HTTP/2 contains some exciting new features that we've previously gone over in the article Utilizing HTTP2 PUSH in a Single Page Application.
In this article, we will: Learn about modules with side effects Understand how CanJS removed side effects in plugins See a preview of how plugins in views might work
The first, and most important step to supporting stability and innovation within CanJS's codebase has been breaking up CanJS into individual repositories, each with its own npm package and semantic version number. In this article, we will discuss: The benefits of independent repositories. How we manage a codebase split across many repositories.