The Ember undertaking is happy to announce the discharge of Ember v6.11. This can be a normal minor launch as a part of the normal Ember Launch Practice course of. This launch is comparatively gentle, contemplating the massive issues that we now have launched lately, however comprises some very helpful bugfixes and enhancements 💪
Ember.js 6.11
Ember.js 6.11 introduces no new options, fixes one bug associated to utilizing the brand new @ember/reactive namespace in Basic builds (for these not but utilizing the default Embroider+Vite construct), and ships one minor enhancement that improves the developer expertise of individuals utilizing auto-complete in an IDE.
Including @ember/reactive to the AMD bundles.
If you’re already utilizing the brand new default Vite-based construct system you’ll be able to skip this one as a result of it solely impacts individuals nonetheless on the Basic ember-cli-based construct system.
@ember/reactive was launched in Ember@6.8 and gives built-in monitoring utilities for widespread assortment sorts (you’ll be able to learn extra about it within the In-built monitoring utilities for widespread collections RFC). For anybody already constructing their apps on Vite, or on Embroider@3 with Webpack and the staticEmberSource: true setting turned on, they’d have been in a position to import from @ember/reactive with none drawback.
Ember apps nonetheless utilizing ember-cli for his or her construct system do not use the sub-packages from the ember-source npm package deal immediately, however as a substitute depend on a pre-compiled vendor asset that defines all of the “packages” accessible to import utilizing AMD. This bugfix makes positive that @ember/reactive is included in these pre-compiled AMD bundles. To grasp extra in regards to the AMD bundles you’ll be able to take a look at the Deprecate Ember Vendor Bundles RFC that explains extra of the context.
Fastened in emberjs/ember.js PR#21024
Rename default export GlimmerComponent to Element for autocomplete DX
This can be a very minor enhancement to the internals of the Ember codebase that helps give higher hints to TypeScript autocomplete. You may learn extra about it within the description of PR #21014 that added this enhancement however the brief abstract is that if you find yourself typing “Element” in your editor (reminiscent of VSCode), you’d by no means get an autocomplete suggestion so as to add the import assertion:
import Element from '@glimmer/part'
It’s because the inner identify for the default export from @glimmer/part was truly known as “GlimmerComponent”. Now once you write “Element” in your editor you may be given a alternative between @glimmer/part or @ember/part.
Launched in emberjs/ember.js PR#21014
Ember CLI v6.11
Ember CLI had no new options, however mounted one bug within the configuration of babel for newly generated apps.
Repair decorator-transforms runtime path in babel.config.mjs
Within the @ember/app-blueprint@6.10.0 the babel.config.cjs was moved to babel.config.mjs. For many instances this does not make any distinction. The one factor that may change when transferring from CommonJS to ESM is the way you resolve different modules. In CommonJS, in Node, you should use require.resolve() to get the path to a different module utilizing Node decision guidelines. We used this within the default babel config to resolve the trail to the runtime module you want for decorator-transforms. When swapping to ESM, it is advisable replace any require.resolve() to make use of the newer import.meta.resolve() operate to find that module. This could trigger a refined drawback as a result of import.meta.resolve() doesn’t return a path however as a substitute it returns a fileURL. The components of babel that must learn the trail to the runtime module for decorator-transforms do not perceive fileURLs so we wanted to move the fileURL returned from import.meta.resolve() via the fileURLToPath() operate.
This alteration has additionally been backported to @ember/app-blueprint@6.10.5
Fastened in ember-cli/ember-app-blueprint PR#226
Thank You!
As a community-driven open-source undertaking with an formidable scope, every of those releases serves as a reminder that the Ember undertaking wouldn’t have been doable with out your continued assist. We’re extraordinarily grateful to our contributors for his or her efforts.
