Recently on GitHub, someone accused Dojo 2 of being vapourware. This opinion came from a position of misinformation. I was glad the individual then engaged with the Dojo 2 project to understand where we are today. We are making swift progress and a beta is on the horizon. It has taken Dojo 2 a long time to get here and to really solidify our vision. We first started brainstorming about plans for 2.0 almost 5 years ago! Around a year ago we solidified our plans and have been unwavering in moving down that path.
I attended the Microsoft Edge Web Summit in San Francisco. I will be honest, outside of meeting a few people, I wasn’t expecting much. Instead, I found myself face-to-face with the “new” Microsoft. I have grown accustomed to the openness and true collaboration that the TypeScript team have engaged in, but I wasn’t expecting seeing this mode
infecting cross-pollinating the rest of the company. What I saw was far from a marketing ploy. It felt as if Microsoft was going through a revolution from the inside out.
Adam Klien, software engineer at Google, announced on ESDiscuss that they were withdrawing the proposal to implement
Object.observe and plan to remove it from V8 by the end of the year.
Object.observe, they assured me the other browsers would eventually implement the rest of Web Components. I also missed that Polymer 1.0 abandoned
You can use Intern to test just about everything! How about testing your Grunt tasks? Even though Intern focuses on tests authored as AMD modules, it certainly can be used to test CommonJS modules, like those used with Grunt. (As well as TypeScript, ES6 modules, and non-module code)
Why would you want to test your Grunt tasks under Intern? Well, for all of the advantages that Intern brings, like integrated code coverage analysis, CI integration, etc. In a lot of cases, your Grunt tasks might be part of a larger project and you can use the same tool to fully test your Grunt tasks. In addition, you can encapsulate all of your Grunt configuration and execution without having to have a
Gruntfile.js as part of your project (or at least have your test configuration separated from your “real”
Gruntfile.js). So even if you just want to support Grunt, but not use Grunt for your task orchestration, you can. This way you can cover all of your code, including your build tooling, in one place. End-to-end test coverage nirvana!