The Ember challenge is worked up to announce the discharge of Ember v6.12. Following Ember’s Main Model Coverage, model 6.12 would be the last launch of the 6.x collection. This launch of Ember.js is an LTS (Lengthy Time period Assist) candidate. LTS candidates prioritize stability over the addition of recent options, and have an prolonged assist schedule.
Ember.js 6.12
Ember.js 6.12 doesn’t introduce any new options on this launch, however now we have carried out some main enhancements to the interior construction of the repo in preparation for Ember 7.0! We’ve got additionally launched three bugfixes and there aren’t any new deprecations.
Merging the Glimmer and Ember monorepos
It has been over 9 years since we introduced the publication of Glimmer.js as a separate repo with the intention that individuals may use Glimmer independently of Ember. The thought was that you may begin any small app with solely the reactivity layer that Glimmer provides you and “npm set up your solution to Ember”
Loads has modified in each Ember and the broader JavaScript ecosystem since 2017, and with these modifications the necessity for having a separate repository for Glimmer, with separate releases, has gone away. Because the introduction of renderComponent() and the construct system transferring to Embroider and Vite by default in Ember 6.8 we will principally depend on our construct programs to not embody the code you are not utilizing in your bundle.
There are extra enhancements to be made, however merging the Ember and Glimmer monorepos will considerably enhance stability of future releases (all of the check harnesses at the moment are built-in) and make it a lot simpler to make large enhancements to the structure of the ember-source bundle.
The glimmer-vm repo has additionally been archived to speak that there will likely be no extra work merged to that repo. Any @glimmer/* packages that also have to be launched (equivalent to @glimmer/syntax and @glimmer/element) will likely be launched from the Ember monorepo. Related points have additionally been moved to the emberjs/ember.js repo, however should you discover a difficulty that you just assume we must always have moved please reopen it on Ember.js (after doing a fast search 😉).
Bug Fixes
Ember.js 6.12 introduces 3 bugfixes
- #20995
renderComponentrepair error: ‘tried to shut a monitoring body, however one was not open’ - #20996
renderComponentrepair error: ‘Can’t learn property of undefined: studying syscall’ - #21091 Repair
onmodifier error message regression
Ember CLI v6.12
Ember CLI has had quite a few enhancements to the blueprints, just a few bugfixes, and we proceed to cut back the variety of packages which can be reported as deprecated throughout preliminary set up.
Replace traditional blueprint to make use of WarpDrive packages
Since Ember 6.8, whenever you generate a brand new app you’ll get the Embroider and Vite blueprint by default. This has been nice for lots of people however, for no matter motive, some apps have not been in a position to improve to Vite fairly but. As a result of we nonetheless assist constructing apps with ember-cli we’re sustaining a legacy blueprint @ember-tooling/classic-build-app-blueprint.
As a lot as doable we wish to preserve this legacy blueprint updated with what is going on within the trendy default blueprint, however generally modifications can lag just a little. In @ember-tooling/classic-build-app-blueprint@6.12 now we have transformed the ember-data setup to match the WarpDrive setup that was added to the default @ember/app-blueprint in model 6.8.
Replace trendy blueprint to have higher lint setup
The earlier part was about modifications made to the fashionable blueprint that hadn’t but made their solution to the legacy blueprints, this part is in regards to the reverse. Proper earlier than the fashionable software blueprint was forked from the traditional one there have been quite a few enhancements made to the eslint configs that helped catch points with checks and correctness in JS information. In v6.12 we ported these enhancements to the fashionable @ember/app-blueprint.
Convert ember-cli-build.js to an ESM file
As increasingly of our stack turns into absolutely ESM we’re getting nearer to the purpose the place we will add sort: "module" to our bundle.json information and at last think about each file in your stack an ESM file. Till that day lastly occurs we’re changing every of the information that may be transformed to ESM by altering the extension from .js to .mjs. This can simplify a number of the barely complicated syntax that now we have needed to do up till this level.
Progress on the elimination of deprecated npm dependencies
As we talked about in earlier launch blogs, there’s an effort to cut back the variety of deprecation warnings when producing a brand new Ember App. Since this effort has began now we have eliminated half of the deprecated npm dependencies 🎉 Whereas that is nice information there’s nonetheless an extended solution to go, and if anybody is on the lookout for a great way to contribute to Ember this can be a activity that would do with extra assist!
Take away using-amd-bundles deprecations
In Ember 7 we will likely be eradicating the AMD bundles which can be shipped with the ember-source npm bundle. To organize individuals for this transformation we launched the using-amd-bundles deprecation in Ember v6.10 and in Ember v6.12 now we have made positive that there aren’t any extra deprecation warnings displayed whenever you generate both a contemporary @ember/app-bluerpint app or one with the traditional blueprint. Which means that should you use ember-cli-update to replace to six.12 you’ll possible have efficiently cleared the using-amd-bundles deprecation and will likely be prepared for Ember v7 💪
Bug Fixes
Ember CLI v6.12 has additionally launched 3 bugfixes (not already highlighted above)
- #10941 Downgrade
isbinaryfileto keep up node assist - #10932 Take away tracked-built-ins as it’s now truly built-in
- #208 Add
globals.browserto eslint config for TS information
Thank You!
As a community-driven open-source challenge with an bold scope, every of those releases serves as a reminder that the Ember challenge wouldn’t have been doable with out your continued assist. We’re extraordinarily grateful to our contributors for his or her efforts.
