You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ember 4.5 was recently released and it included a few new features for Ember.js around using plain function as helpers, and a new renderSettled test helper. Ember CLI also introduced a few deprecations and various bug fixes.
26
+
Ember 4.5 was recently released and it included a few new features for Ember.js around using plain functions as helpers and a new `renderSettled` test helper. Ember CLI also introduced a few deprecations and various bug fixes.
27
27
28
28
Head on over to the [release post](https://blog.emberjs.com/ember-4-5-released) to get more details.
29
29
@@ -33,9 +33,9 @@ Head on over to the [release post](https://blog.emberjs.com/ember-4-5-released)
33
33
34
34
[Chris Krycho (@chriskrycho)](https://github.com/chriskrycho) published an RFC on [Evolving Ember’s Major Version Process](https://github.com/emberjs/rfcs/pull/830). The RFC proposes to put major versions on a predictable 60-week cadence, similar to the [6-week minor release cadence](https://emberjs.com/releases/).
35
35
36
-
The RFC argues that while [Ember mentions](https://emberjs.com/releases/) that it aims to "make major releases as rare as possible” since it forces development teams to spend time researching the changes and modifying their codebase before they can upgrade, it actually makes upgrades more painful rather than less painful. For Ember users while the major releases may be more rare, they actually become harder over time and for Ember maintainers the planning and coordination required for a major release happens on an ad hoc basis with no ability to plan for it in advance.
36
+
The RFC argues that while [Ember mentions](https://emberjs.com/releases/) that it aims to "make major releases as rare as possible” since it forces development teams to spend time researching the changes and modifying their codebase before they can upgrade, it actually makes upgrades more painful rather than less painful. For Ember users, while the major releases may be more rare, they actually become harder over time and for Ember maintainers the planning and coordination required for a major release happens on an ad hoc basis with no ability to plan for it in advance.
37
37
38
-
Chris presents an alternate way to use SemVer by clarifying how we use major releases and editions, namely: never couple the addition of new features to breaking changes, Ember major versions should only remove deprecated features, and Ember's big releases are labeled as "Editions” and lands as a minor release and is therefore always backwards compatible.
38
+
Chris presents an alternate way to use SemVer by clarifying how we use major releases and editions, namely: never couple the addition of new features to breaking changes, Ember major versions should only remove deprecated features, and Ember's big releases are labeled as "Editions” and lands as a minor release and are therefore always backwards compatible.
39
39
40
40
Read more about the RFC and add your comments on [GitHub](https://github.com/emberjs/rfcs/pull/830)!
41
41
@@ -44,15 +44,15 @@ Read more about the RFC and add your comments on [GitHub](https://github.com/emb
44
44
## [RFC: Standardize npm yarn use ✨](https://github.com/emberjs/rfcs/pull/831)
45
45
46
46
[Mehul Chaudhari (@MehulKChaudhari)](https://github.com/MehulKChaudhari) and [Dhanush Kumar
47
-
(@dhanush027)](https://github.com/dhanush027) have co-authored a 😎 new RFC that focuses on standardizing the use of yarn and npm scripts in the Ember experience rather than using Emberspecific commands. This could better align Ember with norms in the larger JavaScript community.
47
+
(@dhanush027)](https://github.com/dhanush027) have co-authored a 😎 new RFC that focuses on standardizing the use of yarn and npm scripts in the Ember experience rather than using Ember-specific commands. This could better align Ember with norms in the larger JavaScript community.
48
48
49
-
If you're interested in this subject please head over to [the RFC](https://github.com/emberjs/rfcs/pull/831), give it a read and participate by commenting!
49
+
If you're interested in this subject please head over to [the RFC](https://github.com/emberjs/rfcs/pull/831), give it a read, and participate by commenting!
50
50
51
51
---
52
52
53
53
## [RFC: public types for Owner, Transition, RouteInfo in FCP ⌛️](https://twitter.com/emberjs/status/1550796034049277953)
54
54
55
-
The RFC for introducting public types for Owner, Transition, RouteInfo is now in its final comment period so if you're interested in participating in that discussion hurry over to the [RFC](https://github.com/emberjs/rfcs/pull/821) and leave a comment!
55
+
The RFC for introducing public types for Owner, Transition, RouteInfo is now in its final comment period so if you're interested in participating in that discussion hurry over to the [RFC](https://github.com/emberjs/rfcs/pull/821) and leave a comment!
56
56
57
57
---
58
58
@@ -80,9 +80,9 @@ Listen to [the episode](https://www.whiskeywebandwhatnot.fm/developing-orbit-and
80
80
81
81
## [Modern CSS in an embroider enabled app 📖](https://twitter.com/evo1/status/1547312309185511426)
82
82
83
-
[Liam Potter (@evoactivity)](https://github.com/evoactivity) wrote a nice article about how to best use modern approaches to handling CSS in an embroiderenabled Ember app! 🙌
83
+
[Liam Potter (@evoactivity)](https://github.com/evoactivity) wrote a nice article about how to best use modern approaches to handling CSS in an embroider-enabled Ember app! 🙌
84
84
85
-
The article covers setting up PostCSS and Tailwind configs, using Webpack, and more! Go checkout[the article](https://github.com/evoactivity/ember-modern-css/blob/main/README.md) today!
85
+
The article covers setting up PostCSS and Tailwind configs, using Webpack, and more! Go check out[the article](https://github.com/evoactivity/ember-modern-css/blob/main/README.md) today!
0 commit comments