👋 Emberistas! 🐹
Set up fast with
read through the Type Stability for Addons RFC 💠,
stories of becoming a developer 📖,
new LinkedIn group for Ember.js developers 🐹,
practice responsive design in Octane with
farewell Ember A11y Strike Team, hello Working Group for Digital Accessibility 🚀,
and last, but not least, handle asset urls with confidence in Ember & Cordova 📱🐹!
Aseem Taneja (@atej) has created a bash script that automates the setup of some often-used tools in an Ember project. To further enhance your DX, it also recommends VS Code extensions and generates settings to integrate with them.
Based on your selections, you get:
- Linting and formatting with ESLint + Prettier
- Utility-first CSS with Tailwind CSS + PostCSS
- Git hooks with Husky
- Pre-commit linting of staged files with lint-staged
- Adherance to conventional commit messages with commitlint
- A launch configuration for in-editor debugging with VS Code's Debugger for Chrome
Chris Krycho (@chriskrycho) proposed a set of guidelines and tooling recommendations for managing changes as addons adopt TypeScript throughout the Ember ecosystem, as part of the path to making TypeScript a first-class citizen in Ember as a whole.
In the RFC, it proposes to align with Ember’s SemVer and LTS commitments and design workflows to support that policy, so that consumers of Ember addons which publish types are insulated from breaking changes in TypeScript whenever possible. The RFC outlines what needs to happen when we encounter:
- Breaking changes to type definitions
- Non-breaking changes to type definitions
- Bug fixes to type definitions
- Dropping support for previously-supported versions
Read through the full RFC on Type Stability for Addons and leave some feedback!
On Becoming a Developer, you can share your background, the story of how you started, interest in coding, studies, first developer role, and some recommendations for anyone starting or continuing to dive into development. 💻
In her Share your Dev story post, Agathe talks about how meaningful her new website is to her. You can see her passion as a developer shine. 🌟
Each developer's story is unique and insightful and can inspire you to do something you never thought possible. Check it out and be sure to share your own! 😃
In case you didn't know, the Ember A11y Strike Team, formed to address the issue that outlined the technical accessibility issues in new Ember apps will have its final meeting next week 😢 … but fear not, some of the ✨ amazing ✨ work that the Strike Team did will be continued in the Working Group for Digital Accessibility! 🔥
The Working Group will be formed with some of the initial members who were also involved in the Strike Team.
You can read up on some of the work they've been planning for the Working Group here, but you can rest assured that the great work the Strike Team did will be advanced even further!
A huge shout out to everyone who was involved in the Ember A11y Strike Team with a special thank you to the following members who worked so hard to make Ember even more accessible:
- Joseph Sumner (@josephdsumner),
- Rajasegar Chandran (@rajasegar),
- Abhilash (@abhilashlr),
- Jamie White (@jgwhite),
- Ava Gaiety Wroten (@hergaiety),
- Frédéric Soumaré (@hakilebara),
- Benjamin JEGARD (@KamiKillertO),
- Lenora Porter (@lenoraporter),
- Ricardo Mendes (@locks)
- Mel Sumner (@MelSumner) and
- Rob Jackson (@rwjblue)
Container queries allow you to practice responsive design at the component level. A component only needs to know how much space it has to figure out how to best present data.
Inspired by Chad Carbert's
ember-fill-up, Isaac Lee created
ember-container-query that works best with Octane apps that target modern browsers. (IE 11 was excluded due to its lack of support for
Resize Observer API, a possible future direction.)
In addition to responsive design, container queries can also help you learn a few other techniques. We encourage you to check out Isaac's blog posts for more details:
- Use modifiers to practice code composition
- Decide the optimal image to load
- Test apps and addons at multiple resolutions
Shibu Lijack (@shibulijack) created a LinkedIn group for EmberJS enthusiasts. It is a group that welcomes anyone who wants to share and discuss the latest and greatest of Ember.js, such as posts that are shared on the Ember.js blog and Discord channels.
Join the group today and start sharing your blog posts!
If you ever wanted to write native mobile applications using Corber, you might have had questions on how url paths for your assets should look like. Especially if they are supposed to work both natively and in the browser.
But fear not! You can now learn all about it in Beto Cantú's (@betocantu93) recent blog post "Understanding Ember.js Public Assets Path for Browser and Cordova". The post not only explains how asset urls are managed in different version of Ember applications, but also shows you how to write your own handy helper to make url handling a breeze in your next Corber project.
Read the full post on Beto Cantú's blog!
This week we'd like to thank @nbibler, @SergeAstapov, @runspired, @pieter-v, @rwwagner90, @pzuraq, @kategengler, @locks, @Gaurav0, @jayjayjpg, @lenoraporter, @jaredgalanis, @ijlee2, @nvdk and @jdberrocal1 for their contributions to Ember and related repositories! 💖
Wondering about something related to Ember, Ember Data, Glimmer, or addons in the Ember ecosystem, but don't know where to ask? Readers’ Questions are just for you!
Submit your own short and sweet question under bit.ly/ask-ember-core. And don’t worry, there are no silly questions, we appreciate them all - promise! 🤞
That's another wrap! ✨
Abhilash LR, Matthew Roderick, Chris Ng, Aseem Taneja, Isaac Lee, Jessica Jordan, Jared Galanis, Amy Lam and the Learning Team