This week’s news: free ideas for your EmberConf talk, a heads-up that qunitjs has been renamed to qunit, a notification that Glimmer is asynchronously shiny, and an inspiring view into exactly how some patient, smart people have fixed some strange bugs.
On Thursday, the program committee hosted an online brainstorming session for the EmberConf 2018 CfP. You can find the full audio recording of it on here, as well as the recordings from the two previous years. Committee members, core team members, and past speakers shared their perspective on audience questions, including:
We’d like to thank @knownasilya, @raido, @pangratz and @sandstrom for either working on these improvements or reproducing bugs which were fixed this week.
Two new Ember-related RFCs have been created this week: First, an adaptation of the API for acceptance tests leaning to the new QUnit testing API has been proposed. You can read more about the changes here.
The second RFC aims to deprecate the {{link-to}} helper’s disabledWhen property in favor of disabled to unify its usage with that of other built-in components.
Two beta bugfixes landed, including a fix for the Array.replace method (you can read more on the quirky bug here) and for the extraction of route arguments in several Router service methods.
Apart from that, contributors to the Ember package applied the semicolon ES linter rule to the full repo, the accepted parameter types for the escapeExpression String util have been adapted, unneeded JSCS rules have been removed in favor of the already-adopted ESLinting, and more linter related updates landed (1, 2,3). Tests have been improved (1, 2, 3,4, 5,6) and another improvement prevents memory leaks stemming from the meta module.
The addon blueprint has been updated to make use of one of ember-try’s latest features - the useYarn flag to configure whether dependencies should be installed with npm or yarn during testing scenarios. Furthermore, a recursion issue has been fixed related to the detection of ember-cli-shims. Also, documentation about Ember CLI’s experimentshas been created, cleanup work on leftovers from the earlier days of the web has been done, and the hamster emoji alias for ember has been removed. RIP. Finally, a few more support improvements and fixes, landed here, here and there.
This week’s efforts around learning resources focused heavily on the Ember Guides; these included updates to code examples to reflect module imports according to the RFC#176 JavaScript Modules API (1, 2,3), and some other inconsistency fixes (1,2), as well as an illustration update.
Work in Glimmer went into updating the way template metadata is passed in both eager and lazy compilation modes. You can read more about the characteristics of template metadata and the motivation of this PR in its detailed description and on another related PR here. Another change to the glimmer.js package makes use of this newly introduced system for looking up modules and templates to optimize bytecode compilation.
Furthermore, the application’s boot method has been updated to be asynchronous, supporting async rendering paths and incremental rendering.
A bug for allowing the extension of the host application's FastBoot config from the fastbootConfigTree addon hook was fixed with an update to the way configurations are merged in.
