Robert Jackson - Adventures in Open Source

Adventures in Open Source

Sign in Subscribe

Robert Jackson

Wishes: Policy Changes 🧹

Wishes: Policy Changes 🧹

The Ember project must get better about closing the loop on dead ends. Communicating clearly with the community to avoid pitfalls. #EmberJS2019 🛣🗺

Wishes: Packaging Improvements🌴

Wishes: Packaging Improvements🌴

Having a great packaging system is critical to Ember's success. tldr; We really need to adopt Embroider! #EmberJS2019 🛣

An async / await Configuration Adventure

An async / await Configuration Adventure

Ember's new integration testing relies heavily on async / await. Learn how to use it in your app, how to make developer ergonomics even better, and help us make the right choice for new projects by default.

🚀 Ember QUnit Simplification 💅

🚀 Ember QUnit Simplification 💅

emberjs/rfcs#232 [https://github.com/emberjs/rfcs/blob/master/text/0232-simplify-qunit-testing-api.md#qunit-nested-modules-api] was merged a few months ago, and is finally ready for you to start testing out (pun intended 😜) in your projects! Read on for more details about why we're making this change, the details

Broccoli Debugging 👞🐛

A couple of years ago I wrote a blog post entitled Debugging a Broccoli Tree [https://dockyard.com/blog/2015/02/02/debugging-a-broccoli-tree]. That has been the most common resource I give to folks that are having a hard time understanding why a given build pipeline is not behaving as

Git Polishing 💎

Custom git configuration often ends up being something we hone over the course of our development careers, slowly evolving into a perfectly tuned set of non-standard commands (this is much the same as how I feel about my Emacs and Vim configs). As I read this tweet the other day

Enabling Ergonomics 🚐 and Performance 🏎

Frameworks like Ember [https://emberjs.com] and Glimmer [https://glimmerjs.com] are constantly attempting to walk a fine line between runtime performance and developer ergonomics. If we lean too heavily towards developer ergonomics we ship a bunch of extra code which hurts runtime performance, but if we lean too much

Does Glimmer mean the death of Ember? 😱

Glimmer [https://glimmerjs.com/] was recently announced by Tom Dale and Yehuda Katz during EmberConf 2017's Keynote [https://www.youtube.com/watch?v=TEuY4GqwrUE&list=PLXQvI7krqI9pmNGIexukXFaqoKP2Yfzu8] . You can get an excellent overview on the main Ember blog which reviewed the EmberConf 2017 State of the Union [https:

Ember CLI Targets 🎯

From the time that Ember CLI first started supporting transpilation of ES2015 (known as ES6 or ESNext back then), source could be authored in the latest ES version and the tooling would emit code that is ES5 compatible. Being able to author using the current spec version but support older

Deploying Glimmer Apps

While playing around with the newly released Glimmer [https://glimmerjs.com/], I wanted to deploy my demo application so others could poke around with it. In order to facilitate shared solutions between Ember and Glimmer, the Glimmer application structure utilizes the same tooling that full blown Ember apps use, this