Set up fast with ember-new-plus ⚡️, 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 ember-container-query ✨, 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.
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
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! 😃
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.
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.