👋 Emberistas! 🐹
Meet Ember 3.17 🆕,
inform us about your EmberConf expertise ❤️,
examine testing finest practices on the Ember Testing Information 📗,
touch upon the co-located check RFC ⛓,
embrace simpler launch administration to your apps 📦🙌,
discover ways to add CI with GitHub Actions ✅,
and respect the underscore 🙇.
On March 16—simply in time for EmberConf!—Ember 3.17 was formally introduced. This launch marked Ember 3.16 as an LTS and kicked off the three.18 beta cycle.
Ember 3.17 launched these modifications:
- Ember.js
- Considerably up to date the Glimmer rendering engine
- Ember CLI
- Eliminated inside utilization of
RSVPin favor of native guarantees - Eliminated
ember-cli-eslintandember-cli-template-lintin favor ofeslintandember-template-lint - Ensured that
npm checkoryarn checkfails whenlint:jsorlint:hbsfails - Ensured that
npm checkoryarn checkin an addon fails ifember-trysituations fail - Eliminated numerous older experiments (module unification and delayed transpilation)
- Eliminated inside utilization of
To be taught extra about upgrading to Ember 3.17, please go to the Ember Weblog. We encourage you to assist check 3.17 and three.18 beta and report any bugs. Thanks!
This 12 months’s EmberConf featured 25+ distant displays concerning the newest and best in JavaScript and Ember with Emberistas from all around the globe – and the occasion was an enormous success! In case you have not had an opportunity to tune into the livestream this week already, make sure you make amends for the recordings for day 1 (half 1 + half 2) and day 2 (half 1 + half 2) of the convention.
Take a look at all of the associated assets for the talks in the convention notes by Alex DiLiberto (@alexdiliberto). Additionally, keep tuned and observe the EmberConf Twitter account to not miss out on the unique BonusConf periods, which will likely be launched over the subsequent couple of days!
Final, however not least, we have now one request for these of you who attended EmberConf 2020:
Inform us about somebody new that you just received to talk with on the digital conf!
Tell us about your reply to this query both by tweeting us by way of Twitter utilizing the hashtag #EmberConFriends or as a message on the Ember Discord within the #support-ember-times channel. We’ll raffle an unique EmberConf retro sticker set amongst all story writers by April 6, 2020. We’re trying ahead to listen to from you and glad catching up on digital EmberConf!
Dawid Pośliński (@PoslinskiNet) wrote about testing finest practices and which addons to make use of within the newly launched Ember Testing Information v1. The testing information goes via why we want exams to start with. What advantages does testing give us and what gaps are nonetheless current.
Following that, the testing information discusses finest practices in how we architect our testing code. It additionally goes via the right way to use the proper of check. Ought to the check be unit, integration, acceptance, visible regression, and even handbook? These ideas are the constructing blocks to developing efficient exams.
Lastly the information goes via all one of the best addons out there at this time and the right way to use them in testing your software with examples from qunit-dom, ember-test-selectors, ember-cli-timecop, ember-a11y-testing, ember-percy and plenty of extra!
Test it out as a free eBook, on GitHub, or as a PDF!
The standard file structure of Ember apps has undergone a number of modifications all through the years.
Moreover the traditional file structure, customers have additionally been capable of opt-in to the pods structure for some time. And whereas pre-v3.13 Ember customers had been modifying part templates and .js information in two completely different directories, they not too long ago received the prospect to work on part information side-by-side after the implementation of the part template co-location RFC.
One other, latest RFC desires to take the precept of co-location even a step additional: it proposes that check information, e.g. these for rendering exams of a part, needs to be co-located proper subsequent to the respective part class and template information. Past that, the proposal suggests an analogous co-location sample for unit exams of associated routes and controllers, too – with the motivation to enhance the discoverability of exams for software builders.
Able to be taught extra about how this may very well be applied? Make sure to learn the full proposal and to go away your ideas or questions within the feedback under!
Who does not dream of easy-peasy releases? Let easy publishing workflows grow to be your new actuality with create-rwjblue-release-it-setup. Leveraging the instruments from the favored library release-it, it lets you setup your venture swiftly for automated versioning and package deal publishing.
Make your dream of simpler launch administration come true with one single npm command:
npm init rwjblue-release-it-setup
…or a yarn command for that matter:
yarn create rwjblue-release-it-setup
Take a look at the v2 launch web page to be taught extra about all the newest options and enhancements and glad publishing!
Steady integration (CI) and steady deployment could also be abilities that you just get to observe perhaps as soon as on a manufacturing app, relying in your job title. However the reality is, you may observe them (ahem) repeatedly at an early stage for any app, regardless of who you might be. 💗
You would possibly then ask, the place can I discover ways to add CI to my Ember app? Are there cool issues that I can do as a result of I’ve an Ember app?
In his weblog submit, Isaac Lee (@ijlee2) exhibits step-by-step how one can write a GitHub Actions workflow. Due to Ember’s addon ecosystem, you may:
- Cache dependencies (keep away from
yarn/npm set up) - Lint information and dependencies
- Run exams individually from linting
- Cut up exams and run in parallel
- Take Percy snapshots in parallel
For those who wished to resolve these issues or wanted a reference code, look no additional! Suggestions is at all times welcome (you may DM @ijlee2 on Discord).
Steven Elberger (@StevenElberger)‘s weblog submit, “Respect the Underscore,” is a improbable instance of what you may observe as a developer: Doc your bug for posterity, particularly if it failed your app or check suite in a catastrophic method.
Listed here are some questions that you just and your crew can deal with:
- When did you first discover the bug?
- Which options or upgrades had been not too long ago labored on?
- What did you assume brought about the bug?
- How did you get rid of a few of the potentialities?
- What did you do to repair the bug?
As a result of Steven’s writing excellently builds suspense, we cannot dare spoil the twists and ending right here. As an alternative, we encourage you to take a look at the submit!
This week we would wish to thank @kratiahuja, @bobisjan, @nummi, @rwwagner90, @rwjblue, @Gaurav0, @Aswathprabhu, @skaterdav85, @jenweber and @laurmurclar for his or her contributions to Ember and associated repositories! 💖
Questioning about one thing associated to Ember, Ember Information, Glimmer, or addons within the Ember ecosystem, however do not know the place to ask? Readers’ Questions are only for you!
Submit your personal brief and candy query beneath bit.ly/ask-ember-core. And don’t fear, there aren’t any foolish questions, we admire all of them – promise! 🤞
Wish to write for the Ember Occasions? Have a suggestion for subsequent week’s challenge? Be part of us at #support-ember-times on the Ember Neighborhood Discord or ping us @embertimes on Twitter.
Carry on prime of what is been happening in Emberland this week by subscribing to our e-mail publication! You can even discover our posts on the Ember weblog.
That is one other wrap! ✨
Be sort,
Chris Ng, Jessica Jordan, Isaac Lee, Amy Lam and the Studying Group
